search

mtherien / slntools

Solution Tools for Visual Studio - manages solution files
MIT License
28 stars 14 forks source link

GlobalSection(TeamFoundationVersionControl) doesn't always has solution SccLocalPath in index 0 #6

Closed mtherien closed 6 years ago

mtherien commented 6 years ago

The HandleVersionControlLines function in the SolutionFileReader uses the Regex ms_regexParseVersionControlName, which implicitly assumes that the SccLocalPath0 always holds the SccLocalPath for the solution itself. However, our VS2010 has put the solution's SccLocalPath at the bottom, resulting in the exeption "Missing property 'SccProjectUniqueName' for the element #{0} in the global section '{1}'.\nFound: Nothing.\nExpected: A property with the name 'SccProjectUniqueName{0}'." for that SccLocalPath. along with it, it won't read the first project (index 0), because the Regex doesn't match that at all. Attached solution was created by VS2010 after re-binding the solution to source control.

Attachments

IHCProducts.sln

This work item was migrated from CodePlex

CodePlex work item ID: '6355' Vote count: '1'

mtherien commented 6 years ago

[UnknownUser@3/22/2012] Resolved with changeset 68569.

mtherien commented 6 years ago

[UnknownUser@2/14/2013]

mtherien commented 6 years ago

[UnknownUser@5/16/2013]