Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Unite 2023 Registrations are now LIVE! We are thrilled to announce that Unite 2023 Registration is now live and open for all!
    Dismiss Notice
New Forum User Notice Unite 2023 Registrations are now LIVE!

Visual Studio 2019 - No 'Attach to Unity' debug option

Discussion in 'Code Editors & IDEs' started by andrewhoke, Apr 18, 2019.

Page 2 of 2

  1. JohnnyGo-Time

    JohnnyGo-Time

    Joined:
    Aug 8, 2021
    Posts:
    17
    I had the issues above in parallel with the weird behaviour that if I opened my .sln, it would correctly open in VS2022. But if I double-clicked a script in Unity, it would open in a new instance of VS2019 without intellisense etc.

    Having tried all the steps above to no avail...well I should have known better than this, but for me the issue was I had an apostrophe and a space in my project folder and .sln names (I am guessing the culprit was the apostrophe in the foldername.)

    After closing everything and removing non-letters from my folder and .sln names, everything worked correctly.
    Unity 2021.3.2f1 and VS2022 17.2.6
     
    JohnnyGo-Time, Sep 10, 2022
    #51

  2. LtKelleyUSMC

    LtKelleyUSMC

    Joined:
    Oct 6, 2012
    Posts:
    44
    Boy, been bugged about this Debugger tool not working for me in some time, but your answer to unchecking Editor Attaching, then exiting Unity, then Restarting Unity and CHECKING Editor Attaching to TRUE, then exiting Unity, and restarting Unity DID IT FOR ME. THANKS
     
    LtKelleyUSMC, Jan 18, 2023
    #52
Page 2 of 2