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
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
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.