Share via

“Some of the properties associated with the solution could not be read”

  • Article

One day I noticed that all of a sudden an message pops up with text “Some of the properties associated with the solution could not be read”,  when I try to open my project in Visual Studio 2008. I remember that I had changed some build settings at the solution level, but was not sure what this message was all about.

Tried binging for results and figured out that people have faced this issue in VS 2003 and VS 2005. I followed the discussion, which eventually lead to opening up the .sln file in a text editor and figuring out what has really changed. I noticed that under the “Global” section, we have “GlobalSection” section, which actually has the number of projects in the solution along with the .csproj information in it.  I was surprised to see that this section was repeated in my .sln file with different information (the SccNumberOfProjects attribute shows 68 at one place and 69 at other place). As I knew that my solution in fact had only 68 projects, I deleted the section with the incorrect information.  And that was it!!! . The error went away ..

Technorati Tags: Visual Studio 2008,GlobalSection,SccNumberOfProjects

Comments

  • Anonymous
    May 26, 2010
    Great!... This is what I was looking for.. Thanks for the help Rahul.

  • Anonymous
    May 31, 2010
    If this happens with Visual Studio 2010 check for the SccNumberOfProjects property in the .sln file. If it is repeated with different numbers, correct.

  • Anonymous
    November 25, 2010
    Thnxx a lot for the solution .. right on nail.

  • Anonymous
    March 01, 2011
    Ditto on all the comments. That worked for me too!

  • Anonymous
    April 13, 2011
    We have the same issue for many months - not sure what cause this. We finally have a fix. Thanks Rahul.

  • Anonymous
    May 04, 2011
    thanks, this worked for me too

  • Anonymous
    August 03, 2011
    Thanks!!!! It worked for me too after correcting the .sln file (opened in notepad).

  • Anonymous
    August 22, 2011
    The comment has been removed

  • Anonymous
    September 08, 2011
    18 months later and the Rahul's solution still works!... thank you!

  • Anonymous
    November 20, 2011
    You were right about the SccNumberOfProjects in Visual Studio 2010: after I corrected it, it went as smoothly as previously. Thanks

  • Anonymous
    December 07, 2011
    Outstanding, that fixed my problem as well!

  • Anonymous
    January 07, 2012
    FYI, I think this may be due to a bad merge resolution in source control. Thanks for spotting this!

  • Anonymous
    May 07, 2012
    Thanks for the help Rahul.

  • Anonymous
    June 12, 2012
    lol... the old project I'm working on had it repeated three times... nice work.

  • Anonymous
    July 26, 2012
    just what i was looking for...thanks

  • Anonymous
    December 05, 2012
    Thanks, I just had the same problem after upgrading a SRS Project to VS 2010

  • Anonymous
    July 31, 2013
    Perfect solution to my problem. Thanks!

  • Anonymous
    August 19, 2013
    Great thanks, had the same after huge merging

  • Anonymous
    December 04, 2013
    If project not added in .sln file, just right click the .sln and add the missing project using add new Existing Project option.

  • Anonymous
    December 13, 2013
    Same issue in VS2012 with a solution.      Dead on the money!   Thanks!

  • Anonymous
    January 18, 2014
    Confirmed this works for VS2012 problem.

  • Anonymous
    March 23, 2014
    Many thanks, worked perfectly here.

  • Anonymous
    May 05, 2014
    Thanks for the post, worked great for me.

  • Anonymous
    September 09, 2014
    Thank you so much. I had merged wrong the file .sln. I now i fixed it. It work fine for me.

  • Anonymous
    November 03, 2014
    I got around this by going in to the Configuration Manager (C#,VS2012) and unticking and ticking a build, forcing the .sln file to be updated, and the problem went away.

  • Anonymous
    November 19, 2014
    Thank you so much.Worked great for me

  • Anonymous
    March 23, 2015
    My issue was the same except I had a repeat of whole global section to do with TFS which were the same deleting the whole of one section worked great. Thanks for this! :)

  • Anonymous
    August 12, 2015
    VS 2013 duplicated the section. I removed one of them from the sln file and now everything works again. Thnx!

  • Anonymous
    January 03, 2016
    Worked for me. Stay away from TFS if possible!