In case you are still experiencing the problem, run a Developer Command Prompt for Visual Studio as Administrator and use the following command: devenv /setup Try removing the following folder to reset the MEF cache (close Visual Studio before doing this): %localappdata%\Microsoft\VisualStudio\\ComponentModelCache This issue can be due to the Visual Studio MEF cache being corrupted. Do not rename the main Unity executable, as VSTU is only monitoring "Unity.exe" processes.You can try to temporarily stop any extra software to see if it changes something. Some programs, like Team Viewer, can interfere with process detection.Try to temporarily disable your firewall or create rules for allowing TCP/UDP networking between VS and Unity.Try to temporarily disable your antivirus or create exclusion rules for both VS and Unity. Confirm that the Editor Attaching checkbox is enabled.įor more information, see the Unity Preferences documentation. Confirm that Code Optimization On Startup is set to Debug.In the Unity Menu, select Edit / Preferences. Troubleshooting the connection between Unity and Visual Studio Confirm Editor Attaching is enabled or Code Optimization On Startup is set to Debug In this section, you'll find solutions to common issues with Visual Studio Tools for Unity, descriptions of known issues, and learn how you can help improve Visual Studio Tools for Unity by reporting errors.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |