Perforce Issue in Visual Studios 2008?

This could be an issue with a "shared" workspace client being used with P4SCC and Visual Studio. Workspace clients should be unique to each user and machine -- Perforce uses the workspace client to track the contents of a specific machine's workspace Here's how it happens when both users are using the same workspace client: Both Users A and B force sync to the latest revisions using the "standard_1" client. The have table is updated on the server, noting that project "foo" is at revision #12 User B checks out "foo", adds a file, and submits.

Now the have table is updated and notes that project "foo" is at revision #13 in the standard_1 workspace User A now checks out project "foo", adds a file, and submits -- without a conflict -- as revision #14 in the standard_1 workspace, because Perforce thinks that workspace already has #13 The solution is to confirm that each user has a workspace client specification that is unique to their machine. This will separate the have lists for each user workspace, and the warning on edit and conflict on checking in will work every time.

This could be an issue with a "shared" workspace client being used with P4SCC and Visual Studio. Workspace clients should be unique to each user and machine -- Perforce uses the workspace client to track the contents of a specific machine's workspace. Here's how it happens when both users are using the same workspace client: Both Users A and B force sync to the latest revisions using the "standard_1" client.

The have table is updated on the server, noting that project "foo" is at revision #12. User B checks out "foo", adds a file, and submits. Now the have table is updated and notes that project "foo" is at revision #13 in the standard_1 workspace.

User A now checks out project "foo", adds a file, and submits -- without a conflict -- as revision #14 in the standard_1 workspace, because Perforce thinks that workspace already has #13. The solution is to confirm that each user has a workspace client specification that is unique to their machine. This will separate the have lists for each user workspace, and the warning on edit and conflict on checking in will work every time.

I called Perforce last Friday and spoke with a technical representative. He came to the same conclusion after reviewing his notes on our phone call. All of my team members are now using their own workspace client and the issue has been resolved.

Thanks for the post! – Registered User Jun 16 '09 at 15:08.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.