When I open my solution, I get a dialog with this warning. The solution (one web app, one class project) builds without errors.
How can I determine what properties are causing the problem, and resolve the error?
When I open my solution, I get a dialog with this warning. The solution (one web app, one class project) builds without errors.
How can I determine what properties are causing the problem, and resolve the error?
Resolved an identical error message in VS2012 by following Boycs's lead. For me, the problem was two extraneous
GlobalSection(SolutionConfigurationPlatforms) = preSolution
blocks at the bottom of my SLN file.Check your SccNumberOfProjects in your .sln file it may be differs from your actual project number.
I can add one more possible solution - A dodgy merge meant that one of the SccProjectUniqueName/SccProjectName/SccLocalPath stanzas inside the GlobalSection(TeamFoundationVersionControl) section had numbers that weren't unique, even though the SccNumberOfProjects was correct. Fixed up the numbering, error message went away.
VS2015 Update 3. [GlobalSection(TeamFoundationVersionControl) = preSolution] was duplicated in solution file. The bottom duplicate contained a project that has previously removed... so removing that duplicate fixed the issue. I think the duplication was caused by a previous merging problem.
I just fixed a similar issue with a VS2010 solution with 35 projects... The cause was a duplicated
GlobalSection(TeamFoundationVersionControl)
section in the solution file. I closed the solution, removed the duplicate GlobalSection(TeamFoundationVersionControl) config and reloaded the solution and the warning message was gone.
If this is not the issue for you, considering you only have 2 projects I would ditch the busted solution file, create a fresh solution and re-add your two projects...
In VS 2015, I had two of these sections "GlobalSection(TeamFoundationVersionControl) = preSolution"
The first one included the latest project added to the solution, the second one (near the end of the solution file) did not. After deleting the second one, the solution opened in VS 2015 without any errors.