Rick van den Bosch - Blog

... on .NET, software architecture, software development and whatnot

Recent Posts

Tags

News

  • Live space

    Photo blog

    Follow me at twitter

    Rick  van den Bosch

    LinkedIn profile

    Add to Technorati Favorites

    Disclaimer
    The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

Community

Email Notifications

Blogs I read

Interesting links

Archives

"Some of the properties associated with the solution could not be read"

Next to the message in the subject, one of the symptoms we encountered is that although the solution contains some test projects the 'Create private accessor' menu has disappeared. Also, selecting 'Create unit tests...' produces an error. And when editing a testrun config and selecting the 'Code coverage' option, the settings dialog simply closes, without any message.

All these (and probably more) symptoms can occur because of a corrupt solution file. In our case the nested projects section was corrupted. Chances are this is because of some project or solution folder not being removed the way it should have been. Anyway, I tried fixing the solution file by hand but because of too many projects and solution folders this wasn't the way to go. Those GUIDs don't make a file very readable... I made a new solution file, containing the same solution folder structure, and added the existing projects. I overwrote the existing solution file, and that was that. So when you're experiencing any or all of the above symptoms, try building up a new solution file.

Hope this helps.

Technorati tags: , , ,

Comments

Stoney Meyerhoeffer said:

We had the same error in our project.  The MS knowledge base article on teh issue about making sure there are no relative paths to Source Control Provider was fruitless.

Turns out it was caused by a second "GlobalSection(TeamFoundationVersionControl) = preSolution" block in our sln file.  We removed the block that was in error, and the properties couild nto be read message went away.

# December 13, 2007 4:41 PM

Joe said:

This worked for me too. Thanks!

# January 25, 2008 9:58 PM

Further Proof I Lack Self-Control : An Experiment in Scotch said:

Pingback from  Further Proof I Lack Self-Control : An Experiment in Scotch

# March 25, 2008 2:39 PM

Jay said:

I also had 2 TeamFoundationVersionControl GlobalSection's in my sln file, removing one fixed my issues as well.  Cheers.

# April 14, 2008 3:57 PM

Dai Clyant said:

Excellent, exactly what I was looking for too!!

Not to do with Team, but older fashioned VSS 6.0. Duplicate SoureControl section was the cause.

Nice one.

:o)

# May 6, 2008 12:30 PM

Mike Brown said:

+1 on the duplicate globalsection

# August 6, 2008 7:56 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)