Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.0.11
Issue ID
VS-30
Regression
No
Double clicking a .unity file in the Project view opens the file in Visual Studio when VS editor package is installed
Reproduction steps:
1. Open attached project "unityFileOpenInVS.zip"
2. Ensure the External IDE tool is set to Visual Studio via 'Preferences -> External Tools -> External Script Editor'.
3. In Project window, open Assets/Scenes folder
4. Double click on "SampleScene.unity" or "New Scene.unity"
Expected results: Double clicking the .unity scene file opens the scene in the editor.
Actual results: Double clicking the .unity scene file opens the scene YAML file in Visual Studio.
Reproducible with: 1.0.11 (2019.4.24f1, 2020.3.4f1)
Not reproducible with: 2.0.0 (2020.3.4f1), 2.0.7 (2020.3.4f1, 2021.1.2f1, 2021.2.0a13)
Could not test with: 2018.4.34f1 (console errors break project)
Workaround:
Removing the "Visual Studio Editor" package from the project fixes the issue.
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
- Crash on ResizeScriptingList<ScriptingObjectPtr> when passing an undeclared variable to the results parameter for GameObject.FindGameObjectsWithTag
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
- Frame spike due to many TreeRenderer.TreeUpdated calls when repositioning terrains in large Scenes
- Crash on GameObject::RemoveComponentFromGameObjectInternal when reparenting Text GameObjects
- [IL2CPP-GarbageCollector] Changing GCMode might permanently disable GC in a multithreaded context
Resolution Note:
We made major version 2.x.x available for 2019.4 which fixes many issues as well as this one.