Saturday, October 13, 2012


MonoDevelop is the tool that comes with Unity that's used to write scripts. It's invaluable, has phenomenal auto-completion, and really I wouldn't want to code without it.

Somehow I deleted something essential to its operation and it crashes on every save. I'm trying to revive it now with every inch of my technical know how but it may be too far gone.

Edit: (My Solution)

I ended up installing the standalone MonoDevelop, which is actually a much more current version than the one packaged with Unity. It doesn't Sync with Unity quite as well, and you have to be delicate with it, but it's capable of working with a GIT repository on Windows being active in the same folder without crashing (Especially if you disable the GIT plugin), which is more than I can say about the built in Unity version (which was crashing left and right, unable to save anything).

I cannot open files from within Unity, but I can create a complete Unity MonoDevelop project by clicking "Sync MonoDevelop Project" I get all the code completion, the Assembly Browser for Unity functions, the help, the debugging... all I have to do is manually look from the Unity 3D console to the MonoDevelop line number to make everything work. And I can open files from the MonoDevelop project hierarchy. So you know all in all I'm not complaining.

It works 95% of the way, the only inconvenience is I can't directly click on Unity Console errors to have them pop up, and I have to remember to open scripts in the Mono hierarchy, not the Unity one.


  1. When you delete every last remaining trace of a program from your computer, re-install it, and realize that the re-installation remembers what project you were working on and what it's registration code is...

    You did not succeed at accomplishing anything at all.

  2. It's dead. It is very, very, very, very dead. Mono has problem with Git stuff right? But It was working fine.

    Then I played around with uninstallers to clean up my machine.

    It's dead, Bill. It's dead.

  3. One... last... try...

    I'm almost POSITIVE the thing I uninstalled was GTK... LIVE DAMN YOU! PLEASE LIVE!

  4. A grand total of a million hours after I started on this stupid problem, I fixed it myself by using a brute force technique. Man was it exhausting, and I achieved almost nothing, except the continued right to keep developing in the way that makes the most sense to me.

    But assuming you never quit learning, then you could just say I totally dominated the machines and tools available to me and that I'm steadily moving towards becoming a more and more competent developer.

    A good thing I'm a developer and not a programmer, right?