You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the solution parser is the only public and official .sln parser it'd be nice if it supported parsing solution items, which is easy to add. Here's an example syntax:
the solution parser is the only public and official .sln parser
. . . kind of. It was never intended as a general-purpose thing, only to meet MSBuild's needs. I'd love to see solution understanding in a separate library that we could use--if that was done, this would be an obvious feature request there. For MSBuild's internal needs, I'd say no way. But people definitely do (ab)use MSBuild for this purpose.
Parsing all the random solution files out there (including all the quirks of VS going back 20 years + all the quirks of randomly tool generated and hand edited solutions) is not as simple as it seems. This code has stabilized to cope with that more or less so there's certainly value in allowing this to be used in a reusable way.
Currently the solution parser just skips over solution items, here's the code:
http://source.dot.net/#Microsoft.Build/Construction/Solution/SolutionFile.cs,775
Since the solution parser is the only public and official .sln parser it'd be nice if it supported parsing solution items, which is easy to add. Here's an example syntax:
The text was updated successfully, but these errors were encountered: