The following screenshots shows Visual Studio debugging a remote Mono process running on a Linux box.
Breakpoints, current line, and stack traces.
The setup works like this: you run a debugging server on Linux. On Windows you install a Visual Studio extension that provides a Debugging Engine and the configuration tools to start your application.
Then you start your application from Visual Studio (Tools/Launch with Mono) which will send the binaries and debug information over to Linux and execute it.
Showing the disassembled code generated by Mono's JIT
The core of the above work is to get the Windows to Linux debugging functionality enabled. We will have more news when the debugging experience is more complete and we are approaching the time to test drive it.
If you are interested in trying it out, sign up for our preview on our web site.
Mono 2.0 will for the first time include a debugger, the command line mdb command.
Beyond this, we want to offer GUI debugging. The native solution is being built on top of MonoDevelop and will be available when we release MonoDevelop 2.0. It will work on both Linux and MacOS hosts.
The second GUI engine will be the above Visual Studio plugin for developers that use Windows as their main OS and Visual Studio as their IDE.
More Visual Studio Integration
In addition to this work to integrate Visual Studio with Mono for remote debugging, thanks to the Summer of Code (Ed Ropple) and Jonathan Pobst's work in this hack week we got some support to run applications on Mono/Windows and run our Mono Migration Analysis tool.
Jonathan's work is available today as an MSI, check out his post for more details.
You can also check Ed's summer of code report on CloverLeaf.