In some others, the "Attach To Unity" button is replaced by a button that simply says "Start," and an error message pops up when attempting to use it. In my case, when selecting "Attach To Unity," no targets appear in the pop-up window. csprojs in Main, and using "Assets > Open C# project" to regenerate them the VS versions of these files have not reappeared, though I am able to check out and edit in VS without issue. Per the suggestions in this thread and others, I've removed the previously installed UnityVS, in favor of using the version packaged with 5.2 the "About Unity" window says i'm using UnityVS 2.0.0.0. We've got one or two paid VS floating around, and I updated to community 2015 to try to resolve the issue, to no avail. Our company updated to 5.2.0f2 today, and we're unable to attach Visual studio's Debugger to Unity following the upgrade. We'd appreciate if you can be on the lookout for any unforeseen problems there. This required changes in how we deal with "selected script editor", how we generate c# projects (also for monodevelop). Does it work for you? Are you running into problems we didn't foresee? Is there anything obvious that we could do to make it even better? We'd love to get some feedback from people who try it. You can also download VSTU from the microsoft site, but you need to make sure you download it again, as they shipped a new version two days ago, and you need that version.
#Visual studio tools for unity 5 install#
The Unity5.2b3 installer will install this for you if you ask it to install Visual Studio.
This functionality requires the very latest VSTU to work. Unity will only load it if you specify VisualStudio as your preferred external editor. You can check if VSTU is loaded by going to the about window, and checking the bottom left. The "Visual Studio Tools" menu item is also no longer there. You no longer need to have the UnityVS package imported into your project.
Starting with Unity5.2 beta 3, Unity has improved support for UnityVS/VSTU.
0 kommentar(er)
