views:

701

answers:

3

What would a developer used to working in Visual Studio have to give up if they switched to Monodevelop? This hypothetical developer most often develops ASP.NET web applications with C#.

I'm aware that Monodevelop has the basic Visual Studio features like syntax highlighting and support for Visual Studio solutions. What are the deficiencies that would most affect the productivity of a developer giving up Visual Studio?

To keep things consistent, please confine your answers to points about Visual Studio 2008 and Monodevelop 2.0.

A: 

It looks like you've never seen monodevelop before. Yes, it's good and very important software. But at this time it's simply incomparable with VS. VS is more stable, rich and robust software system. Yesterday I've compiled one very important project in monodevelop and it simply crashed...

But it has ASP.NET desinger and ASP.NET MVC plugin. may be it'll be suitable for you

Trickster
I've used monodevelop a little, but not recently. I phrased my question in a general way because I think it's the best way to get an authoritative answer.
ctford
You can also try wine+.net2.0+sharpdevelop2.2. if you on linux.If you on windows and don't want to pay for VS(or you're not a student) my advise is Sharpdevelop. But you can also make contribution to Monodevelop project in some way :-)
Trickster
+3  A: 

I think a lot of developers are used to third-party tools like ReSharper, which you wouldn't be able to get for MonoDevelop.

The number of MonoDevelop users is dwarfed by Visual Studio users, so there is far less online help, such as blog posts.

Joe R
I came from the java world and found studio extremely lacking feature wise, until I installed resharper. +1
Matt Briggs
+1  A: 

When I say "C# editor" in this post, I mean the Visual Studio C# text editor. Sorry, it's just a typing habit. :o

I'll make a guess that the fit and finish of the Visual Studio C# text editor is better than in MonoDevelop. The reason I say this is I've worked on a project in the past and getting the details correct is unbelievably difficult. Here are some items that the Visual Studio C# editor does exceptionally well at that are some of the hardest to duplicate:

  • Speed and accuracy of IntelliSense, although I've documented how to do handle one of its best features. The Visual Studio 2010 editor is even better, and I haven't been able to match it yet (and no one seems to care, so good luck matching this feature set). The IntelliSense engine also does an amazing job handling partially completed (syntactically incorrect) code at a large scale level. It's not as hard to do within statements in a method, but the C# editor is very thorough.
  • Smart Indent is stupid-difficult to do well, and the C# editor does it. Even Visual Studio 2010 Beta 1 had major issues here, but it's improved in Beta 2 and almost up to where 2008 is.
  • Code formatting in the Visual Studio C# editor is excellent. This is much easier than the above two points, so I can see MonoDevelop including it (not sure if it does). The primary difficulty doing it as well as Visual Studio does it is matching the customizability - it just tends to lead to some gross code (though this is only my experience, other people may have a beautiful solution).
280Z28