Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2.0.5
Issue ID
VS-28
Regression
Yes
Can't attach Unity debugger to Visual Studio on a Virtual Machine
How to reproduce:
1. Create a Virtual Machine
2. Open Unity and add any script to any GameObject
3. Open that script with Visual Studio
4. Select "Attach Unity Debugger"
Expected results: Unity Debugger is attached
Actual results: No Unity Client is found
Reproducible with: 2020.2.0b14, 2021.1.0a9
Not reproducible with: 2018.4.30f1, 2019.4.16f1, 2020.1.17f1
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note:
Sorry for the late response to this issue. The issue shows that the Visual Studio Tools for Unity is not correctly installed in Visual Studio (e.g project incompatible when loading). Microsoft has tested this without being able to reproduce it so we are closing as unable to reproduce. We recommend to report the issue directly to Microsoft if you still have the issue. Thank you.