Search Issue Tracker
By Design
Votes
0
Found in
2019.2.0b7
Issue ID
1168707
Regression
No
[Hub] Visual Studio is not selected as current External Script Editor when installing Unity together with Visual Studio 2019
Reproduction steps:
1. Open Unity Hub
2. Go to the "Installs" menu click "Add"
3. Choose and Install Unity 2019.2.0b9 together with Visual Studio 2019
4. Open any Project and go to "Edit" -> "Preferences" -> "External Tools"
Expected result: "External Script Editor" dropdown has newly installed "Visual Studio 2019" as a current selection
Actual result: "External Script Editor" dropdown has "Open by file extension" as a current selection
Reproduces on: 2.0.3
Note:
- Before reproducing the issue, make sure all the Visual Studio versions are uninstalled and "devenv.exe" is not marked as current External Script Editor
Comments (2)
-
ScottHawkins
Nov 02, 2019 17:40
Why is this marked as "by design" when the "actual result" does not match the "expected result"?? The "expected result" is what I would have expected...
God bless this gentleman who posted a fix:
https://forum.unity.com/threads/installed-unity-edit-preferences-external-script-editor-did-not-recognize-visual-studio.733592/
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:
Improvement feature planned. currently VS only suggested when not detected