Visual Studio 2017 and Unity: Attach to Process not available

Unity Engine
1

I have Windows 10 Home 64-bit using Visual Studio 2017 Community and Unity 2017.1.

I installed Unity with a pre-existing installation of VS 2017. I loaded Visual Studio from Unity, but it cannot debug the project (no “Attach to Unity” button). I uninstalled Unity and reinstalled it, this time checking to install VS 2017. This did not change the situation. This occurs when VS is run as an administrator as well.

I cannot find a VSTU version beyond VS 2015: Visual Studio 2015 Tools for Unity - Visual Studio Marketplace

Visual Studio can't "Attach to Unity" - Unity Engine - Unity Discussions, which was resolved by having Xamarin, but I don’t and never had Xamarin on this computer.

Visual studio can't attach to unity editor. - Questions & Answers - Unity Discussions, but I have the latest version of VSTU and the unity executable is already called Unity.exe (with .exe being the file extension, not part of the filename, of course).

Here are my two options thus far:
- I can revert to VS 2015 and try VSTU tools (which I cannot do for other reasons).
- I can revert to MonoDevelop and see if it can’t natively debug Unity.

Please read everything above. Surely somebody else has had this problem.

2

VSTU is built-in in VS 2017. You can find ‘Attach Unity Debugger’ from the VS ‘Debug’ menu, the 4th item from the top.

1 Like
3

I had this issue as well, for VS2017 Tools for Unity installed. I could not see any button for attach to unity, nor was the process listed under Run>Attach to process.

The trick is to go to Run>Attach to process…>change the little dropdown button below that reads ‘Debugger: .Net Core Debugger’ to Debugger: Unity Debugger’ and the Unity Engine process will now show up in the list.

Spent 3 hours to figure this little thing out. sigh