search

zetanove / dependency-analyser

Automatically exported from code.google.com/p/dependency-analyser
0 stars 0 forks source link

Support .sln files for newer versions of visual studio #4

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Pretty self explanatory.

Original issue reported on code.google.com by drewnoakes on 22 Apr 2011 at 9:11

GoogleCodeExporter commented 9 years ago 
Don't know if it's the same issue, but I get the following error in 
v1.1.4141.28255 when attempting to open any VS 2008 SLN (might be related to 
running on Win 7 64?):

I don't have any VS 2005 SLN files to compare with.

************** Exception Text **************
System.ApplicationException: Doesn't appear to be a valid Visual Studio 
Solution file
   at Drew.DependencyAnalyser.SolutionFileAnalyser.ExtractProjectInfoFromSolution(String content)
   at Drew.DependencyAnalyser.SolutionFileAnalyser..ctor(FileStream solutionFileStream)
   at Drew.DependencyAnalyser.DependencyAnalyserForm.menuFileOpen_Click(Object sender, EventArgs e)
   at System.Windows.Forms.MenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.MenuItem.MenuItemData.Execute()
   at System.Windows.Forms.Command.Invoke()
   at System.Windows.Forms.Command.DispatchID(Int32 id)
   at System.Windows.Forms.Control.WmCommand(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Original comment by dhoc...@gmail.com on 24 May 2011 at 3:25

GoogleCodeExporter commented 9 years ago 
Hi yes, the error you're seeing is exactly related to this issue.  The tool has 
to parse the .sln and .csproj files, but it doesn't like the format of such 
files which are newer than VS2003 (IIRC).  We need to add support for newer 
file formats, which shouldn't be too hard.  Patches welcome :)

Original comment by drewnoakes on 24 May 2011 at 4:26

GoogleCodeExporter commented 9 years ago 
Hey there,

will this ever be updated. Just found out about this (potentiallz) awesome 
tool, but it doesn't work with my VS2013 (or VS2010) files. Would be very cool!

Original comment by TheOneAn...@googlemail.com on 8 Apr 2014 at 1:25

GoogleCodeExporter commented 9 years ago 
I haven't looked into this. The fix should be straightforward, and a patch 
would be welcome.

If you don't wish to fix this you could point the application at your 
application's DLL files instead or your SLN file.

Original comment by drewnoakes on 16 Apr 2014 at 11:35