[MonoDevelop] Planning MonoDevelop 1.0

Michael Hutchinson m.j.hutchinson at gmail.com
Thu Nov 23 18:22:47 EST 2006

On 11/23/06, monodevelop-list.1.tracyanne at spamgourmet.com
<monodevelop-list.1.tracyanne at spamgourmet.com> wrote:
> For me MonoDevelop would be sufficiently complete to be usable if it has
> a functioning ASP.NET Visual Designer, and if the context menu in coding

I'm afraid you'll have to prepare to be disappointed. I will try to
ensure the the Visual Designer is stable with its current feature set,
but it is still lacking in some major areas (see
http://mono-project.com/AspNetEdit#Plans). Several tasks would be made
much easier and cleaner by other projects that are still quite
nebulous, such as Mono/XPCOM integration of some kind, and Mozilla's
Composer2, so I'm happy to concentrate on other areas and wait to see
if these materialise.

To sum up, it'll still take a lot of work to make AspNetEdit
"complete" IMO, so I feel my time is better spent polishing the
ASP.NET project support at the moment. If there are any points you'd
like to make regarding which features should be prioritised, please
do. I have had surprisingly few contributions at all for the editor,
including constructive criticism. Code would also be very welcome :)

Michael Hutchinson

More information about the Monodevelop-list mailing list