Search Issue Tracker
Fixed in 2019.4.X
Votes
0
Found in
2019.4.24f1
2019.4.26f1
Issue ID
1336788
Regression
Yes
Visual Studio is not an option to choose from as an External Script Editor by default
Reproduction steps:
1. Open the attached "ExternalScriptEditor.zip" project
2. Reset Preferences (Edit > Reset Preferences)
3. Open the External Script Editor drop-down menu (Edit (Windows) or Unity (macOS) > Preferences > External Tools > External Script Editor)
Expected result: Visual Studio is in the External Script Editor drop-down menu since it's installed and has built-in support
Actual result: Visual Studio is not in the External Script Editor drop-down menu
Reproducible with: 2019.4.24f1, 2019.4.27f1
Not reproducible with: 2018.4.35f1, 2019.4.23f1, 2019.4.28f1, 2021.2.0a19
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
Resolution Note (fix version 2019.4):
Fixed in 2019.4.28f1