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
- Call stack hyperlinks become unclickable when scrolled down in the Console window
- Package files do not get checked out in Perforce when the project includes a provider callback
- Editor freezes when changing Gradient or AnimationCurve fields with the runtime binding system
- VFX throw errors upon importing it
- "NullReferenceException" error is thrown when swapping between built-in and URP depending on assets loaded out of asset bundles
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.