Had the same issue. It seems when VS does take too long to start, Unity does launch MonoDevelop instead.
What did help is renaming "MonoDevelop.exe" to something like "MonoDevelop2.exe"
↧