Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
2.0.1
Issue ID
1243391
Regression
Yes
[Visual Studio] Opening a script opens the default VS version for .cs files instead of the one set as External Script Editor
Steps to reproduce:
1. Open the project from the attached file "1243391.zip"
2. Go to Edit > Preferences > External Tools
3. In the External Script Editor drop-down select Visual Studio Community 2017
4. From Assets, open NewBehaviourScript.cs
Expected result: Script is opened in Visual Studio 2017
Actual result: Script is opened in windows default Visual Studio version for .cs files
Reproducible with: Visual Studio Editor 2.0.1(2020.1.0b10, 2020.2.0a13)
Not reproducible with: Visual Studio Editor 1.1.1(2019.3.15f1), Visual Studio Editor 2.0.0(2020.1.0b10, 2020.2.0a13)
Could not test with: 2018.4.23f1(Visual Studio Editor not available in Package Manager)
Notes:
- when testing the default VS version is 2019
- to reproduce, make sure that the version set as External Script Editor is not the same as the default version.
- right-clicking on the script and selecting "Open c# Project", opens the correct VS version
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #1242949