Something in TFS screwed a SCC references in one of the .csproj files at a client.
As a result, it generated strange build errors (unfound projects in the wrong branch), because when loading project from the correct, the IDE in fact loads it from the wrong branch.
When you read the blog post from the Microsoft TFS development support team, the solution looks simple: in a regular project the values for SccProjectName, SccLocalPath, SccAuxPath and SccProvider should all be SAK (indicating the SCC should ignore their values).
That is only 1 piece of the solution. Somehow, Visual Studio and/or TFS seem to cache some information in hidden places, so it keeps insisting to use the project from the wrong branch.
So, in addition to changing the above SAK values in the project in the correct branch, you need to:
- Also check (and if wrong change) the above values to SAK for the project in the wrong branch
- Remove the references to the project in the wrong branch from the Visual Studio MRU list in the registry (HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\ProjectMRUList)
- Delete the .suo file for the good solution
- Add the project from the correct branch to the solution
- Manually modify the .sln file in the correct branch to remove the relative directory paths to the project in the wrong branch (values in keys named like SccProjectUniqueName58, SccProjectName58 and SccLocalPath58)
- Reload the solution in Visual Studio and check everything works correctly
It took at least a couple of hours to find this all out, for these reeasons: Read the rest of this entry »
Like this:
Like Loading...