[MonoDevelop] Visual Studio 2005 Import

Marek Sieradzki marek.sieradzki at gmail.com
Thu Sep 21 11:51:10 EDT 2006

Dnia 21-09-2006, czw o godzinie 17:07 +0200, "Andrés G. Aragoneses
[ knocte ]" napisał(a):
> >> Is everybody for native support for VS.NET?
> I wouldn't imagine why anybody would not be happy with this... Well, 
> perhaps someone may think giving this support will imply that nobody 
> uses again the MD project/solution types (which BTW I consider much 
> better than the VS ones because they are all XML-based) because VS 
> doesn't have support for them and then the choice will always be for the 
> most supported format.
You're wrong. Microsoft's .sln files even if not xml based are just a
list of projects in solution. Everything that is inside of .*proj can be
modified. That isn't possible in MonoDevelop projects' case.

> >> I think native support would provide needed functionality and high
> >> flexibility for users to switch between VS.NET, SD and MD. Especially as
> >> VS.NET developers would not switch over immediately, it is process and
> >> native support would allow them to test drive MD without having to convert
> >> their projects. I know this was a feature that I requested, back in the days
> >> when I was test-driving SD.
> > 
> > Also, once the project is loaded into MD, it should be semi-trivial to
> > allow "Save as MD Project."
> Then, why not offering an option to work with MD and VS solution types 
> simultaneously (whenever you save, you update the .SLN/.??PROJ and the 
> .MDS/.MDP files)?
> Oh, and I hope that if you or someone implements native support, it 
> doesn't mean that MD doesn't offer the Import utility anymore ;)

MonoDevelop will have it when someone implements it. I personally don't
see any reason why would anyone need import instead of native support.

Marek Sieradzki <marek.sieradzki at gmail.com>

More information about the Monodevelop-list mailing list