[MonoDevelop] Monodevelop in Windows

Michael Hutchinson m.j.hutchinson at gmail.com
Sun Feb 8 21:13:46 EST 2009

On Sun, Feb 8, 2009 at 7:25 PM, Alfredo Cuaresma
<alfredocuaresma at yahoo.es> wrote:
> Hello,
> After looking this article,
> http://mjhutchinson.com/journal/2009/02/07/monodevelop_vista64
> it seems he has gotten a fully port of Monodevelop for Windows Vista 64bits,
> without using cygwin or autotools, compiled using VS2008. It is working.
> has anyone tried this port of Monodevelop to Win64? Could be there a packet
> of this in the web for downloading? (It is an attractive way to offer a
> solution for Windows users for using Mono easily).

I won't offer binaries right now, because it's not ready for end users
at all; there are still bugs that prevent it being useful for
anything, and hence it would present a poor impression. Developers are
welcome to build it and contribute fixes.

There were a few rationales behind the work I've been doing. The order

* Running MD on .NET means we can debug it in Visual Studio, which is
useful because the Mono debugger only works on Linux. This will make
it much easier to stabilise MD on Windows, which will be useful when
running MD on Mono on Windows.

* Running MD on .NET also helps to find GTK# bugs in Windows, and
Mono/.NET incompatibilities that MD depends on.

*  Getting MD to build without autotools means that people can work on
MonoDevelop without touching autotools. This applies to using MD on
Linux and the Mac, as well as VS on Windows.

*  Being able to run MD on .NET is useful for people who want to use
it as the basic of a crossplatform IDE without requiring their Windows
users to install Mono.

* Loading a large MD-created project in VS is a good test of MD's
project support.

Note that "using Mono" via MonoDevelop would require MonoDevelop to
run on Mono, which hasn't been the focus of my work so far. However,
this will become easier as a result of my work.

Michael Hutchinson

More information about the Monodevelop-list mailing list