For apparently no reason, every time I open my solution, Visual Studio checks the sln file out.
If I compare it to the previous version there are no changes. But this is really frustrating since everybody has the solution checked out.
I'm using VS 2008 and TFS 2008, both SP2.
Any idea on how I can stop this thing to happen? Or is a feature/bug of the TFS source control provider for VS?
From memory, if you use the Tools, Options menu and select the Source Control, Environments panel there should be a few options for configuring the way the IDE interfaces with the version control.
I think some of these options control the checkout on open behaviour.
Just in case, like me, you couldn't get it to work and you find that one or more projects also get checked out, I found a simplier solution. Make a note of the project(s) that it keeps checking out. Go to File - Source Control - Change Source Control, and then unbind the projects in question. Click OK, Save All, then go back into Change Source Control and bind teh project back to the solution. Hopefully this will work for others
Allow the check-out and then compare both files. If VS added something like
<Service Include="{B4F97281-0DBD-4835-9ED8-7DFB966E87FF}" />
you are experiencing a VS bug with a solution in VS2008 but not ported to VS2005
Check this link for further details:
Although not preventing the problem in the first place, liberal use of the Team Foundation Power Tools "Undo Unchanged" command will (surprise surprise) undo the pending edit if no changes have been made.
Are you saving your files before do the comparison? It happened with me some time ago and keep saying there are no changes between the files, but after some time I realize I wasn't saving the files before and it was comparing with the version in disk, not the version in memory.
Every time you open some solution in Visual Studio, it performs some operations which may cause your .sln or project files change and then it will ask you to check out the file. It happens when there are changes in the folder structure in the developers machine, or when they don't have the same versions of all the files. Maybe someone added a project in some folder and another developer has the same project in another place. Another case I see this happen was when we have an solution with some c++ projects, for some reason, one of this c++ projects had a .res file with absolutes paths. Once this file was generated automatically by VS it kept change from developer machine to developer machine.
I would suggest you to open your .sln file and look for some absolute paths or by relative paths which may not exist in some developer machine, depending what files they Get from yours Source Control.