Search Issue Tracker

Fixed in 4.5.3

Votes

167

Found in

4.3.0f4

Issue ID

568656

Regression

Yes

Double clicking a C# script will open MonoDevelop instead of Visual Studio

CodeEditors

-

Repro steps:
1. Set Visual Studio as your external code editor in Preferences and double click on a C# script.
2. A popup box saying "Starting Visual Studio" shows up, but then it disappears and MonoDevelop opens instead.

Update 2014-06-12 please go for this URL or a discussion of the fix for this bug in 4.5.1p1 and beyond: http://forum.unity3d.com/threads/double-clicking-a-c-script-should-open-visual-studio.251358/

Update 2014-08-01 A few remaining fixes for these Visual Studio launching problems have landed and will be available in 4.5.3p1. These fixes include:

* Additional retries when a new Visual Studio session is busy while Unity attempts to open a solution file or script file.
* New logging of information about the Visual Studio detection and launching process to the editor log.

Comments (64)

  1. master2k27

    Mar 01, 2014 17:21

    I want VS 2013 , opens mono or VS 2010

  2. SnappEd

    Feb 28, 2014 11:16

    Still happens most of the time. Probably even more annoying is that it doesn't have every time!

  3. ekt

    Feb 15, 2014 22:27

    same here

  4. joserene

    Feb 11, 2014 22:14

    Please address this... a workaround would be fine, but having a $10,000 licence for a software you can't use is QUITE hurtful.

  5. dreidy

    Feb 10, 2014 18:50

    It pretty much ignores any option in the drop-down. Changing the .sln and .csproj to the expected tools and versions for 2013 doesn't work either.

  6. xenstalker

    Feb 05, 2014 03:57

    Same issue.
    Windows 7/8 64-bit and VS2013

  7. Zenix

    Jan 30, 2014 00:29

    Ridiculous that this is still happening. It's been 3 years (at least) now and they can't get a .cs file to open in the specified editor...

  8. Raiden-Freeman

    Jan 19, 2014 10:37

    Win7 64 + VS 2013, happens sometimes.

  9. musiko

    Jan 16, 2014 09:01

    Same here.
    Win7 Pro 64-bit + Unity Pro 4.3.2f1 + VS 2012 Express

  10. yurka

    Jan 14, 2014 15:55

    Problem is still there in 4.3.3. I'm forced to downgrade to 4.2 again, total waste of time.

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.