I\'m having issues getting Visual Studio\'s debugger to attach to Unity - editing and compiling scripts inside VS is working fine - however, when clicking \"Attach to Unity\
This is indeed a compatibility issue between VSTU and XamarinVS. We worked with Xamarin and we already fixed this in our master.
We will release a new VSTU version with the fix and additional features shortly.
Regards Sebastien Lebreton [MSFT]
This was killing me too. After going through everything installed in the last few days and uninstalling and reinstalling, I determined that the latest Xamarin broke VSTU integration. I even reverted to VSTU 2.1 to no avail.
Only uninstalling Xamarin allowed the debugger to attach to Unity.
So for now, we have to use either Xamarin or VSTU, but not both on the same machine if we want the VS debugger to attach to Unity.
Two days thrown away trying to reinstall just EVERYTHING.... (PS: latest Xamarin "stable" update broke iOS debugging on iPhone via usb, just to let you know too....).
I had the same problem, except that the tool didn't print any unity process... Uninstalling Xamarin as well didn't help, and in fact I was just not able at all to attach unity throw the tool. (Attach process did worked, but no breakpoint in code can be reached).
In fact, it was because I renamed "Unity.exe" to Unity "5.3.4f1.exe".
Visual Studio Tools for Unity need to attach to the process Unity, and no other name can be handle for now.