Search Issue Tracker
Fixed in 5.3.0
Votes
1
Found in
5.2.0f1
Issue ID
721553
Regression
No
[OSX] Open C# project open both builtin Monodevelop and external editor
To Reproduce:
1. Set external script editor to Xamarin Studio.
2. Open any solution with 'Assets / Open C# Project'
Only Reproducible on OSX, opening script manually just open Xamarin Studio as expected.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
lukaszunity
Oct 19, 2015 06:49
@edwood75: If you are still experiencing issues, please submit a bug report.
@reapazor: Could you post this to the scripting forums (http://forum.unity3d.com/forums/scripting.12/) and send me a PM on the forums with a link to your post? I would like to avoid using the issue tracker for this.
Reapazor
Oct 17, 2015 12:30
As directed by Shawn,
When I set the code editor editor preferences, and refresh the preferences window to show the updated "Code" editor selected, Unity still opens MonoDevelop.
The particular code can be found here:
https://github.com/dotBunny/VSCode/blob/master/Plugins/Editor/VSCode.cs
Currently, Line 816 starts the UpdateUnityPreferences which does the swap of the prefs.
Any ideas what I might be doing wrong?
lukaszunity
Oct 12, 2015 08:38
@edwood75: Are you setting your external script editor to Xamarin Studio or another editor?
edwood75
Oct 04, 2015 07:34
Well it not fixed. I just installed Unity 5.2.1p1 and it still persists. As noted in many threads, whats wrong with your testing team? You keep notifying issues as fixed when they are not.
Do you take in consideration the time and hassle to download/install the supposedly "good version" keeping the projects intact by moving around or migrating just to realize that the problem remains???
lukaszunity
Sep 28, 2015 08:50
Fixed in Unity 5.2.1p1