ChatGPT解决这个技术问题 Extra ChatGPT

How to stop Visual Studio from "always" checking out solution files?

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?

do you have a unit test project as part of the solution?
TFS supports concurrent checkouts, and as long as there is not modification to the .sln file multiple checkout are not a problem.
When *.sln files have actual changes, they are a horrific nightmare to merge because the projects within are given arbitrary-but-not-unique IDs. I'm a big advocate for concurrent checkouts, but I keep most of our *.sln locked.
THIS IS FIXED IN VS2013!!! I open same solution in 2012 and it checks out .sln, open in 2013 and it stays clear.
I have seen this from time to time with all versions back from Visual Studio 2010 and up to the newest version, Visual Studio 2015 Update 3. It happens around half of the times I open a solution, and it seems to be more frequent for solutions with many projects.

G
Graham Clark

This happens when the following is in the .sln file:

GlobalSection(ExtensibilityGlobals) = postSolution
    MyGlobalProperty = AnyValue
EndGlobalSection

I found that Enterprise Library added one of these. I removed it, checked in the solution, closed then re-opened it, and no more automatic check out.


Looks like the Unity NuGet package may have done this to my solution file in VS 2010. I removed this section and my auto-checkout problem was solved. Thanks Graham!
two of my favorite technologies - TFS and EntLib - what a pair of darlings.
I have such a section but do not want to remove it since it contains data I want to keep - what now? MS closed this issue as "not reproducible" - stupid? connect.microsoft.com/VisualStudio/feedback/details/573538/…
Dan's comment adds the needed info -- it's not necessary to remove all global sections -- just the part that seems to get added in by the unity nuget package.
This works. I had a NuGet reference in a GlobalSection just as described in this answer. The solution file was checked out without any changes every time it was opened. Removed this section and the solution file is no longer checked out automatically.
j
jussij

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.


yes... they allow you to checkout automatically, prompt from checkout, or do nothing... but nothing that helps with this problem
can't you then just say "no, don't check out" when it prompts you?
I wish I was the only developer in the team... unfortunately I cannot rely an all developers being diligent
CodeClimber, every time you start VS it does an automatic check out and you want that to stop and turning off the automatic check out does option not fix the issue. What the?
For those who don't have the "Environments" in their list of options, change your connection from "Local" to "Server" (source: stackoverflow.com/questions/26843300/…)
J
JJ76

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


D
Dave Roberts

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.


Updated link for Team Foundation Power Tools: marketplace.visualstudio.com/…
a
abatishchev

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:


No project in the solution has this line of XML
N
Nigel Belham

The Visual Studio Solution file is being silently checked-out through one or more of the Solution's Projects using the Microsoft Enterprise Library - I believe this is something to do with the Enterprise Library Configuration Utility which allows the configuration management of the various Application Blocks - http://msdn.microsoft.com/en-us/library/ff649479.aspx

See this Microsoft Feedback posting: http://connect.microsoft.com/VisualStudio/feedback/details/737184/globalsection-extensibilityglobals-postsolution-checks-out-sln-file-on-open


thanks for the link Nigel, all the team are experiencing this issue
R
Richard Berg

It is a feature/bug of one of the project systems being loaded within the solution. Try removing various types of projects (C#, VB, C++, web site, web app, unit test, silverlight...) until it goes away; that's your answer.


C
Carlos

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.