Search Issue Tracker

Fixed in 5.3.0



Found in


Issue ID




MonoDevelop fails to fully open from within Unity



When the JavaScript script file is double-clicked in Unity editor for the first time after restarting computer, MonoDevelop fails to fully load and an error pop-up message similar to this is shown:

Error while trying to load the project 'C:\Users\Public\Documents\Unity Projects\4-3.3f1_AngryBots\Assembly-CSharp-firstpass.csproj': Object reference not set to an instance of an object.

Reproduced with:
Unity Version 4.3.1f1 (cebd4d9b5122)
Unity Version 4.3.3f1 (c8ca9b6b9936)

Comments (14)

  1. HubertRonald

    Sep 23, 2017 13:26

    Thank you JESUSLUVSYOOH your suggestion works for me !

  2. uncleGe

    Apr 12, 2016 18:10

    Yup, JESUSLUVSYOOH's solution (on previous page) fixed me right up!

  3. mkondor

    Feb 19, 2016 15:00

    Created a new project, first time to open the first script I created got this error (Unity v5.3.2f1)

  4. abstractfragment

    Jan 11, 2016 19:15

    Jesus' solution did not work for me :c. It's already selected and booting Monodevelop on its own also fails.

  5. Ozgar

    Dec 09, 2015 04:04

    I upgraded to 5.3 and now this issue has started for me.

  6. Cachimery

    Nov 13, 2015 18:29

    The solution of JESUSLUVSYOOH works for me, thanks.

  7. Keg85

    Jun 29, 2015 09:27

    I also have this issue, but tried JESUSLUVSYOOH's solution has not worked for me as Monodevelop is already selected.

    It is only after the computer is restarted once I close the message and restart Unity and click the script it works fine again until reboot.

  8. zeeshancan

    Jun 23, 2015 15:57

    how do you reproduce it. please explain it in brief

  9. BlackPanda

    Mar 27, 2015 05:17

    Wow! That's one good solution. It worked for me! Still, Unity guys should solve this bug.

  10. amarnaman

    Oct 16, 2014 09:52

    Well, who'd have believed it, Jesus really does save (at least when it comes to Unity issues). I was sceptical but it worked for me. Just follow the steps and select your MonoDevelop.exe (wherever it may be) and then restart Unity (and MonoDevelop). No repeat occurrence of the problem!

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.