MonoDevelop Launch Failure

Questions & Answers
1

I just updated unity to Unity 4.1.4f1 and when I try to edit a script through MonoDevelop i get this error:

System.IO.FileLoadException: Could not load file or assembly 'Mono.Cairo, Version=2.0.0.0, Culture=neutral, PublicKeyToken=0738eb9f132ed756' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

File name: 'Mono.Cairo, Version=2.0.0.0, Culture=neutral, PublicKeyToken=0738eb9f132ed756'

   at MonoDevelop.Components.Docking.ShadedContainer.DrawBackground(Widget w, Rectangle allocation)

   at MonoDevelop.Components.Docking.ShadedContainer.DrawBackground(Widget w) in c:\BuildAgent\work\f07246b5212f7be4\monodevelop\main\src\core\MonoDevelop.Ide\MonoDevelop.Components.Docking\ShadedContainer.cs:line 184

   at MonoDevelop.Ide.Gui.SdiDragNotebook.OnExposeEvent(EventExpose evnt) in c:\BuildAgent\work\f07246b5212f7be4\monodevelop\main\src\core\MonoDevelop.Ide\MonoDevelop.Ide.Gui\DefaultWorkbench.cs:line 1379

   at Gtk.Widget.exposeevent_cb(IntPtr widget, IntPtr evnt)



WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind failure logging.

To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Not being able to edit my code through MonoDevelop completely halts development of my game, does anyone know of a solution to this problem, or even a substitute for MonoDevelop that is as good or better.

2

Install 4.1.5 which has a fix for broken MD in 4.1.4. (Still doesn’t fully work on Win8, however.)

3

4.1.5f1 was working fine for me for a while, then it started crashing with a similar error message to you. I believe what triggered it was attaching the debugger to the Unity process, but I’m not sure. Deleting everything in the project except for Assets and Project Settings did not fix the issue. I reinstalled 4.1.3, and now things work again.