Breaking this out into it's own thread because I'm afraid it's getting lost among the other larger issue. So, with Unity 5.2 VS integration. Unity currently ignores the UnityVS plugin. This is correct behavior on Windows but OS-X users still rely on the plugin to manually create a UnityVS solution and to connect to the Unity instance. There are many Mac users that run Visual Studio in parallels or VMWare that rely on the VSTU plugin. We currently don't have a workaround and cannot use 5.2 until we have this fix. Now, if there was someway for Unity to auto-detect our Visual Studio install on our parallels share, that would be even better, but I have a client project that needs to be upgraded to 5.2 soon and I'm going to be left in the lurch unless I get some kind of solution soon.