search

mtherien / slntools

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

error reading Visual Studio 2013 .sln files #10

Closed mtherien closed 6 years ago

mtherien commented 6 years ago

I'm using SLNTools.Core 1.1.1. When I try to read a Visual Studio 2013 .sln files, I get this error:

unable to read solution files with: Additional information: Invalid line read on line #4. Found: VisualStudioVersion = 12.0.20827.3 Expected: A line beginning with 'Project(' or 'Global'.

Visual Studio adds a couple of additional headers: Visual Studio 2013 VisualStudioVersion = 12.0.20827.3 MinimumVisualStudioVersion = 10.0.40219.1

As a workaround, I've been deleting those properties manually, but it would be cool to not have to do that.

btw, I just uploaded the binary to NuGet, because it wasn't there. http://www.nuget.org/packages/SLNTools.Core/

Attachments

fix_read_vs2013.diff

This work item was migrated from CodePlex

CodePlex work item ID: '7650' Vote count: '2'

mtherien commented 6 years ago

[prograholic@1/14/2014] I created patch which fix this issue: i determine version of SLN file (assume that first line in SLN contains version) and depending on version perform reading of header of SLN file. Attach contains this fix

mtherien commented 6 years ago

[Greg_at_eSolar@1/14/2014] I get the exact same error using VS 2012 :-(
Huge bummer... I was really looking to see if this tool would be the solution (pun intended) to my SLN woes!

mtherien commented 6 years ago

[Greg_at_eSolar@1/14/2014] Actually on closer inspection the issue was that one of the developers was using 2013 :-(

mtherien commented 6 years ago

[UnknownUser@1/24/2014]

mtherien commented 6 years ago

[ctaggart@1/25/2014] Thanks for the new build Christian. I pushed the updated library to NuGet. https://www.nuget.org/packages/SLNTools.Core/

It is super easy to do. Let me know if you want me to transfer ownership to you. Also note that you left the versions as 1.1.1.0. Not a big deal.

mtherien commented 6 years ago

Issue closed by christianwarren with comment Fixed in version 1.1.2.

Reason closed Fixed