We have 2 developers working on a project that is located in Vault (SourceSafe drop-in replacement). As normal in a SCC environment each developer checks out the files they are editing then checks them back in when they are complete. To ensure working with the latest files each developer has VS.NET set to automatically get the latest version upon opening a solution. The solution contains about 15 projects, some of which were upgraded from VS.NET 2003 and some of which were created in VS.NET 2005.
The problem is that each time a developer opens the solution after the other developer has checked-in a project VS.NET prompts the developer to checkout the project. Apparently there's something in the project files that is changed by each developer's machine when a project is loaded. Does anyone have ANY idea what this could be? It is really annnoying as each developer has to constantly checkout projects, etc. What settings in the project file could be causing this "race" like situation?
The sequence of events is something like this:
1. Developer A opens the solution and gets all projects.
2. Developer A makes a change to the project file (adds a file, etc).
3. Developer A checks in the project
4. Developer B opens the solution and gets all projects
5. VS.NET 2005 prompts Developer B to checkout the project
6. Developer B checks out the project then checks it in
7. Developer A gets latest version of the project
8. VS.NET prompts Developer A to checkout the project
And on and on and on and on. Well, you get the point, I think.