[MonoDevelop] Planning MonoDevelop 1.0

[Paulo Aboim Pinto]

Hello to all

For this thread I would like to give my contribution. First of all I use
to be a Micro$oft programmer and I use use all day the VS2005. There is
some issues that I would like to insert. 


On Thu, 2006-11-23 at 00:28 +0100, Lluis Sanchez wrote:
>       * Debugger: I know a lot of people will ask for this, but I fear
>         the debugger won't be ready by our code freeze date. We can
>         release it later on as a separate add-in.

I would be the first guy that want this, but at this time we can use the
man/power and do anything else. 

>       * Text editor: There are several requests/issues to solve: 
>               * Parameter completion: after typing the name of a method,
>                 show a popup window with information about the
>                 parameters the method takes. 
>               * Remove C#-isms. The code completion engine has several
>                 C#-isms in the code, which may make it difficult to
>                 integrate with other languages. 
>               * Configurable key bindings. That's not specific to the
>                 editor, but people mostly complain about it. I'm not
>                 sure we can implement this for 1.0. 
>               * Refactory operations. We have and under-used refactory
>                 API. It would be nice to use it to implement some basic
>                 refactoring operations.

In the Text Editor beside the Reflection (this is a huge point) I would
like that MD Text Editor should be able to Collapse and Decollapse
#regions.
With this we could organize our code better.

Other feature that should be easy to implement is the comment of class
or methods. Using /// command, the Text Editor should enter all the
prototype of the Class or Method comment. That information should be
exported to a MonoDoc File.  

Resolve some problems with identation.

>       * ASP.NET support: I don't know if this add-in can be mature
>         enough for the 1.0 release. I'll need input on that (which
>         features could we release? would the add-in be really useful for
>         real world web projects?).

That will not be good. I develop most of my application with ASP.NET

> 
>       * NUnit: It can be considered feature complete for 1.0. The only
>         missing issue to resolve is what to do with the NUnit
>         dependency. Right now the add-in can't be built with recent
>         NUnit versions since they have breaking changes. I talked about
>         this with Charlie Poole in the Mono summit and he suggested to
>         embed the most recent NUnit dlls into the add-in, since even if
>         the API has some breaking changes, new NUnit versions can still
>         run tests written for all the previous versions.

Why should we have TDD integration in MonoDevelop? One of the good
things in TDD software is that we can right-click on a Test Method and
run it from there.
How hard will be to implement this?