This weekend I took some time to try and port the MonoDevelop.Debugger.Soft.Unity addins to Xamarin Studio. As it turns out it wouldn’t work, even when the addin compiled and loaded, because it relied on functionality that was added to the base MonoDebugger.Debugger.Soft namespace by Levi Bard; this add-in is built with MonoDevelop/Xamarin so instead I elected to fork the MonoDevelop 4.0 project from github, reintegrate these changes and build a MonoDevelop 4.0 package with the Unity soft debugger included.

After about a day of work I am now able to use MonoDevelop 4.0 to connect, and debug for Unity. While everything does appear to work, there is a warning that popsup when I launch the game about an object being garbage collected, but pressing OK will get you through it. Perhaps I’ll look into why this happens soon.

In the mean time, grab the MonoDevelop-Unity 4.0.6 build here: (OSX | Windows). Dont forget to grab mono and Gtk# over at http://www.go-mono.com/mono-downloads/download.html

GitHub: MonoDevelop fork, MonoDevelop.Debugger.Soft.Unity fork

Edit: I’ve spoken with one of the kind developers at the MonoDevelop project, in the next two weeks I’m going to begin work on pushing necessary improvements to the main repository for MonoDevelop and build a MonoDevelop Add-in to more easily distribute the Unity Soft Debugger. This should (in theory) make it compatible with MonoDevelop 4 and Xamarin Studio once complete.

Update 2013-07-04 – Work on making a more robust add-in is nearly complete. I am working with the MonoDevelop project to get a couple of changes pushed which I expect to be done this weekend, then I merely have to prepare the addin package to be included in the MonoDevelop/Xamarin addin repository. I’ll post again once I have more updates.