Path already mapped in another workspace (via Dennis van de Laar)

I experienced an issue with Visual Studio 2008 Team Explorer where I couldn’t remap a certain local solution to a solution in TFS due to workspace conflicts. I removed all workspaces used in the VS2008 and tried to remap again but with no luck. Apparently some of the mapping information is stored in TFS cache on the guest machine itself.

Thanks to Dennis van de Laar and his blog post, I found the path to the cached information and deleted them. Remapping the solution worked flawlessly after that.

You can find the cached information in: C:\Documents and Settings\[user]\Local Settings\Application Data\Microsoft\Team Foundation\2.0\Cache\

Today we ran into a little problem with workspaces. We have a VPC with our projectcode in VS2003. We are using the MSSCCI provider to connect to the Team Foundation Server. When i want to share my VPC with another project member we logically ran into a SID problem. We ran the tool NewSid to make sure that our VPC’s have a different Identity. To make sure that the other project member works on another workspace we also created a new TFS account. T … Read More

via Dennis van de Laar