4.3 is set up to open scripts in VS 2013 but opens MonoDevelop instead

Unity Engine
1

This is a weird issue I started having today.
Unity is set up to open scripts in VS but when I doubleclick any script it starts MonoDevelop.
VS 2013 Ultimate. Everything was working fine with 4.2.

Anyone has same behavior?
Anyone knows maybe there’s a config file or stuck path to MonoDevelop which does this stuff?

It’s getting very annoying )8

2

Odd. Yours is the only post I’ve seen on this. I thought I was the only one.
Just found the same thing except I have VS 2008 pro.

I tried the browse option, but that re-selects the same devenv,exe.
I can only ever open MonoDevelop no matter what I do in preferences so far.

So at the moment it’s MonoDevelop or nothing which is a pity as I really miss the row/column numbers at the bottom right and the toolbar.

edit
Now it’s getting more annoying. I went back to 4.2.2 and I am still having the same problem - MonoDevelop or nothing. Double-clicking a .cs file brings up VS as I’d expect.

3

What is the extension set to open with by default in the OS?

4

When I doubleclick sln or cs files they are opened in VS.
But doubleclicking scripts in Unity opens them in MonoDevelop.

If you go to project folder and open solution in VS manually Unity keeps opening scripts in this instance of VS though.

5

Hi there, I’m experiencing a similar problem.

I have recently installed Visual Studio 2013 and upgraded Unity to 4.3. I used to work with VS2010 as the default editor. Now I have set the default editor to Visual Studio 2013 but whenever I try to open a script from inspector, VS2010 opens up instead.

Additional Info:

  • If I delete the devenv.exe for VS2010, Unity launches MonoDevelop even though VS2013 is selected as default editor.
  • My setup at my other computer is the same, everything works fine there.
  • It worked fine with Unity 4.2.2

Hopefully we’ll get some new ideas on how to fix this.

6

Reported this issue as a bug.

7

I’ve also found that, if I open “ProjectName-csharp.sln” manually with VS 2013, then the Unity inspector opens any scripts with VS 2013 in the opened solution and does not try to open VS 2010 anymore until the project is closed. So until it is fixed, this may be a solution for you as well, just open the csharp.sln with VS manually.

8

From what I’ve seen Unity4.3 opens the VS2010 editor but has trouble with VS2008 and VS2013.

I had VS2008 and as reported by a few others, it can only open MonoDevelop with a doubleclick on the script. I then installed VS2010 and now Unity3d happily opens VS2010 editor…

… except it seems to have problems with scripts that have previously been opened by MonoDevelop. If I open an old MonoDevelop’ed script with VS2010 and remove methods it can give strange Unity errors after I save it.

Another quirk of the new MonoDevelop is that when you doubleclick a script from Unity4.3 it will give you 2 copies of the script in MonoDevelop if you were using that script in a previous session.

This is becoming quite strange and a distraction from coding.

9

Hi guys,

This is a known issue which is already assigned to developers. However, it has a low priority, so users have to promote it by voting. Developers will draw attention to this and will fix it faster.

Also, please leave a comment with information: OS version, Unity version, Visual Studio version.

Vote here:

Cheers.

10

Great! Let’s vote!

11

I’m having the same issue. Voted it up. Only info I have is that it happened after a system crash because of power outage.

12

A friend found this:

He was having a similar problem, this did it for him. Didn’t get the chance to try it out myself yet.

Also for VS 2013, you may want to do the same thing with 12.0 IDE folder instead of 11.0 IDE