Scripting Visual Studio Breakpoints

Hi guys.
Pre-Unity 5.2 I was happily using UnityVS with Visual Studio Ultimate 2013.
I installed Unity 5.2 to find it has support for VS out of the box.
So I uninstalled Microsoft Visual Studio Tools for Unity.
Now I don't know how to attach for debugging breakpoints, previously I pressed Attach to Unity, which has been replaced by Start.

Any insights?

 

Hi,

Jb from the VSTU team here.

Unity 5.2 still requires the VS Tools for Unity.

Please make sure you install the VS Tools for Unity 2.1, if you're using 2013 that would be there:

http://visualstudiogallery.msdn.microsoft.com/20b80b8c-659b-45ef-96c1-437828fe7cf2

Please also make sure you go through our short documentation about setting up Unity 5.2 to work with VSTU:

http://unityvs.com/documentation/native-support/

 

That's weird. I installed Unity 5.2 yesterday and I didn't get the VSTU automatically (didn't have VSTU at all before, thus the reason why I installed 5.2). I had to go into the Visual Studio and install it through the Extensions-place.

 

@Maisey

My installer looks like this, it has an entry for VSTU. How does it look in your case?



If it looks the same, did the installation fail despite the item being checked?

 

Thanks guys. I think I was confused because I still had UnityVS.OpenFile as an option for External Script Editor, so I uninstalled VS Tools so as not to conflict. It's fine now after reinstalling.

 

It looked the same, I had unchecked "Web Player" and "Example Project". Can't possible imagine that I unchecked the "Visual Studio Tools for Unity" when that was the reason I even installed 5.2.

 

When not downloading the special installer (636 KB) but the Editor-only installer, for example "Unity Editor (64 Bit)" found under "Additional Downloads" ("UnitySetup64-5.2.0f3.exe", 1.2 GB), the checkbox options within the installation process will be different. In my example the only checkbox option is "MonoDevelop".

Using that full Editor-only installer means downloading only once and installing it plenty times without further downloading. Simply saves bandwidth.

I highly suggest that even the special installer includes a checkbox option to install MonoDevelop because the Microsoft Visual Studio Community 2015 cannot be used by everyone. Our company makes more money than allowed for the Community Edition. The programmers in my team use Visual Studio 2013 Professional but the game designers and graphic artists do not, simply because of the cost of Visual Studio. When those occasionally have a look into a C# script they use the MonoDevelop included in Unity.

 

It may be useful for you to note that while using the special installer that downloads the UnitySetup for you, you can opt to save the installer file in a location of your choice.

We have one team member download the installer and then move the downloaded installer to a shared drive for all to use.