Search Issue Tracker
By Design
Votes
1
Found in
2017.4
2018.4
2019.2
2019.2.1f1
2019.3
2020.1
Issue ID
1200385
Regression
No
Unity project names are missing in Visual Studio 2017 when attaching with Unity Debugger if multiple Unity instances are open
Steps to reproduce:
1. Download and open attached Unity project
2. Create a new Unity project and open it aswell
3. Using "Visual Studio 2017" open debugLog.cs file found in the attached project
4. In the Visual Studio window press "Debug" and then "Attach Unity Debugger"
Expected outcome: You can see the names of both open Unity projects in the "Select Unity Instance" window
Actual outcome: Only one or even none Unity project names are displayed in the "Select Unity Instance" window
Reproduced with: 2017.4.35f1, 2018.4.13f1, 2019.2.14f1, 2019.3.0f1, 2020.1.0a14
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 UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
Resolution Note (2020.1.X):
This has only been fixed in Visual Studio 2019. For this to be fixed you would have to contact the Microsoft team to request a backport of their changes to the Visual Studio 2017.