Javascript required
Skip to content Skip to sidebar Skip to footer
Home / Vs2016 Some of the Properties Associated With the Solution Could Not Be Read.

Vs2016 Some of the Properties Associated With the Solution Could Not Be Read.

Stack OverflowVisual Studio warning: "Some of the properties associated with the solution could not be read"

[ https://stackoverflow.com/questions/6190402/visual-studio-warning-some-of-the-backdrop-associated-with-the-solution-coul ]

[+292] [2011-06-21 23:33:52] Boycs [Accepted]

I just fixed a similar issue with a VS2010 solution with 35 projects... The crusade was a duplicated

GlobalSection(TeamFoundationVersionControl)

section in the solution file. I airtight the solution, removed the duplicate GlobalSection(TeamFoundationVersionControl) config and reloaded the solution and the warning message was gone.

If this is not the upshot for you lot, because you only have ii projects I would ditch the busted solution file, create a fresh solution and re-add your two projects...


1

[+39] [2017-06-08 12:13:51] Saber

The best solution is to strength the VS to regenerate the configs. To do this:

  1. Open the sln file with a text editor.
  2. Scroll down till you achieve the last "EndProject" element.
  3. Delete everything afterwards that.
  4. Relieve, Shut and rebuild the solution and everything will be regenerated.

two

[+34] [2014-03-07 09:thirty:27] bicbmx

Seems similar there is a number of reasons for this warning. I was getting it because my solution file SccNumberOfProjects = 4 when there was but 3.


3

[+8] [2013-04-nineteen 14:52:05] Ben Mosher

I only fixed a like event in VS2012 with 44 projects.

The crusade was a combination of a duplicated GlobalSection(TeamFoundationVersionControl) section (a la Boycs' answer), but I also had several projects duplicated--as well every bit a few references to projects which had been recently removed--within the GlobalSection(TeamFoundationVersionControl) department that I kept.

Once I had ensured that all of the referenced projects corresponded i:ane with actual projects in my solution, the warning went away.

Aside: I suspect that the majority of these issues could take been avoided with closer attention paid to the .sln during branch and commit merges, but who knows what VS is thinking sometimes...


four

[+6] [2014-04-01 xiv:15:09] CThin

I had a multitude of the errors above. I renamed the project, saved closed, reopened changed the proper noun back. This recreates the .sln file and in my case took out all the extra items.


5

[+4] [2016-eleven-25 10:47:nineteen] TheWho

The other answers already explicate how to fix the problem. Mayhap I tin aid to non get the problem again:

How I got the problem Our solution file got mixed up when I added a new projection to information technology, while another developer also added a new project and committed his changes (which I didn't got at my local system). When I started to commit my changes, I had to merge the .sln file, where I obviously messed up :-)

What I learned

Solution files are awful to merge. If you lot add a project practice the following: 1. Go latest Version 2. Add your project 3. Commit

If you come across your solution file under pending changes, only y'all don't run into a change in the compare mode, yous take to press 'Save All'. While adding your new project, VisualStudio likewise altered the solution. All the same, this is an unsaved modify at the moment.


6

[+3] [2013-09-06 21:39:05] BitPusher16

Resolved an identical error bulletin in VS2012 by post-obit Boycs'south lead. For me, the problem was two extraneous GlobalSection(SolutionConfigurationPlatforms) = preSolution blocks at the bottom of my SLN file.


seven

[+2] [2015-01-26 07:59:35] papaiatis

For me the problem was empty spaces (due to re-create-paste) at the stop of each line. By removing them I didn't get the error again.


8

[+ii] [2016-09-07 12:58:50] Papa Stahl

In VS 2015, I had ii of these sections "GlobalSection(TeamFoundationVersionControl) = preSolution"

The first one included the latest project added to the solution, the second one (well-nigh the end of the solution file) did not. Later on deleting the second one, the solution opened in VS 2015 without any errors.


9

[+1] [2018-03-26 thirteen:eighteen:53] Ali Karaca

Check your SccNumberOfProjects in your .sln file it may exist differs from your actual project number.


10

[0] [2013-10-31 11:37:43] Yossi B

i fixed similar trouble in vs2012.

in my example the problem was that the SccProjectName0 property value inside GlobalSection in the MySolutionName.sln file was empty.

i solved it by setting SccProjectName0 value with copy of this string value from another solution, and replacing the name of the project in the cord to the current 1 (BTW - if your project name as infinite in information technology (' '), information technology need to supersede with '\u0020').

*

in my case the trouble begin after i mistakenly opened solution controlled by TFS with one-time MySolutionName.sln file of the aforementioned solution from time that this solution was controlled by VSS.


11

[0] [2016-xi-02 08:59:28] Moutono

VS2015 Update three. [GlobalSection(TeamFoundationVersionControl) = preSolution] was duplicated in solution file. The lesser duplicate contained a project that has previously removed... and then removing that indistinguishable stock-still the consequence. I think the duplication was caused by a previous merging problem.


12

[0] [2018-10-08 02:47:57] Julian Melville

I tin add 1 more than 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 right. Fixed upwardly the numbering, mistake message went abroad.


13

[0] [2019-04-05 15:xv:40] GrayDwarf

VS 2019 - I was opening a VS 2017 project for the kickoff fourth dimension in VS 2019. In the Output window, click the "Show output from:" DDL and review your options because you may see additional fault information.

In my case, the solution was to simply re-configure my source command mappings for 2019.

  • Go into Squad Explorer
  • Click the Manage Connections push (plug)
  • Click Manage Connections link and Connect to a Project...
  • ...

14

[0] [2020-12-xi 11:24:35] Srinivas Ch

For my case, it was the order of projects, make sure following tags with number at end are consistent and sequential.

  1. SccProjectUniqueName
  2. SccProjectTopLevelParentUniqueName
  3. SccProjectName
  4. SccLocalPath

xv

[-1] [2016-07-13 06:47:09] Zoltán Nyakas

I had the aforementioned trouble, and my solution is:

  1. Open the solution in VS
  2. Ready the Solution Platform to Default
  3. Save information technology
  4. Close the VS
  5. Open the .sln file in Notepad++ (or any other editor)
  6. Delete all of the other Solution Platform item from everywhere
  7. (for example:{73E03C8F-1F76-45E2-9D45-FA040A63F0AA}.Release|Whatsoever CPU.Build.0 = Release|Any CPU)
  8. Save it, and reopen the solution.

This works for me.


16

wagstaffjobill.blogspot.com

Source: http://www.stackprinter.com/export?service=stackoverflow&question=6190402&printer=false&linktohome=true