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
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.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- SpeedTree importer fails to import .st files when path to the project includes a special character
- [VFX Graph] HSLS Redefinition error when input have the same name as attributes
- [VFX Graph] HLSL VFXFIXED_RAND isn't working
- Crash on Meta Quest 2 when using Vulkan
- Greyed out Icon for Tool Context is misaligned in the Tools Overlay in the URP 3D Sample Template
Forgon
May 23, 2014 12:21
I have the same issue with win7 and vs2013.
I had vs2010 before and I uninstalled it and installed vs2013. But since visual studio uninstall is not clean some files remained. At first that did not cause any problems but when windows update installed a visual studio 2010 update for some reason and all things break for Unity.
Unity was trying to open visual studio 2010 instead of 2013 and was crashing. So I tried uninstalling the update, but then Unity was completely ignoring vs2013 and opening up Monodevelop instead. Also the windows update kept coming up and installing when I was shutting down and moving me back to square one.
So I found a workaround till this bug is fixed.
1- Move or rename monodevelop executable/directory
2- Move or rename Visual Studio 2010's devenv.exe (You can find it at C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE )
If you do these steps it will open up CS files in Visual Studio 2013. However for new projects it will not create the project files. So if you have a new project first open it up in Monodevelop to build the project files and then remove Monodevelop.
So now you can open up the project file directly from the project folder with vs2013 and when you double click on errors or cs files it will open them up with vs 2013. However for errors and debug.logs, it will still not take you to the right line. You have to use CTRL-G to go to that line.
curryjl
May 21, 2014 17:21
@RVKENNEDY Great idea! Works for me.
mdrotar
May 14, 2014 20:45
I started having this issue today with VS 2010 opening up instead of VS 2013. It started happening right after I installed some windows updates which included updates to VS2010.
Unity 4.3.4, Win 7
Reloder
May 14, 2014 11:41
it's openning the vs2010 or monodevelop instead of vs2013..
i was forced to remove the vs2010 and monodevelop to fix it.
but now, when i open a script it open only the cs file himself without the whole solution of the project
hope it be fixed soon
viper110110
May 10, 2014 15:46
I get this bug except sometimes it is VS 2010 instead of 2013. Ultimate versions of both. Found in 4.3.4
Saxi
May 09, 2014 15:04
This needs to be fixed, it is maddening.
laurentOngaro
Apr 21, 2014 09:35
same problem
windows 8.1 pro
unity 4.3.4f1
VS 2013
the solution proposed by RVKENNEDY (renaming monodevelop exe) works for me
Flickayy
Apr 15, 2014 14:15
Stoped working the other day.
When trying to manually open project-csharp.sln from inside VS. VS stops working.
When trying to open a script in the editor, MonoDevelop is opened instead of VS.
Visual Studio 2013 Update 2 RC.
Windows 7 Home Premium x64
angelsin
Apr 03, 2014 03:21
win 8.1 vs 2013. used to work fine, stopped working randomly today
rvkennedy
Mar 27, 2014 15:34
As a workaround, move or rename "C:\Program Files (x86)\Unity\MonoDevelop\bin/MonoDevelop.exe". Then Unity will correctly spawn Visual Studio instead. It still won't attach to an existing running instance, so you'll get a blank solution with the cs file in the editor. But at least you'll be in the right editor.