I've reinstalled Visual Studio 2015 community and VSTU 2.1 but it still doesn't work.Įdit: I've noticed that the Visual Studio app I can add trough the "Browse." function is an app generated by VMware and acts as an shortcut. Using "Open C# Project" opens MonoDevelop and Visual Studio but it can't resolve anything from the Unity API. Double clicking a file will open the file in Visual Studio but it won't load the project. I've added Visual Studio as a External Editor trough the browse function. Before 5.2 I was able to use this setup perfectly with the VSTU unitypackage, but now with 5.2 I am having trouble to get Unity to see if VSTU is installed so it doesn't generate the correct project files.
I'm running Unity on a Mac and Visual Studio 2015 trough VMware. It may seem like other plugins can also cause the integration to fail. Mac users running Visual Studio on a VM doesn't have working integration Users of the Resharper plugin cannot open scripts from Unity without first opening Visual Studio manually There are some instances where integration used to work in 5.1 + UnityVS, where it doesn't work anymore.
dll causes both of them to fail hard.īig props to the dev team for adding VS tools as a standard feature in Unity.ĮDIT: As you can see by following this thread, the UnityVS integration isn't quite there. It seems like having both the new built-in VS tools and the old. Upgrading to Unity 5.2 broke VS Tools for Unity for me - VS tools was unselectable in the External Script Editor drop-down, and opening any script caused MonoDevelop to open and promptly fail to load anything if "normal" visual studio was selected.Īll of this was fixed by simply deleting the VS tools folder from the Assets folder of the project. This might've been a fluke, but in case it's consistent, I'll post this: The problems in the original post were all gone for me some time during 2016.
UPDATE: Since people keep posting here to bring the post back up to the top: