11 Mar 2015

permalink

Unity 5 was released last week at GDC, and it comes with a few changes from Unity 4.

The Visual Studio Tools for Unity 2.0 will support Unity 5 completely, in the meantime there's a few actions you can do to have the Visual Studio Tools for Unity 2.0 Preview work nicely with Unity 5.

Visual Studio Tools Unity Package



The first thing that you'll notice is that you don't find the Visual Studio Tools package in the Import Package menu.

You can easily import the Visual Studio Tools package by importing it manually. Chose Import Custom Package, and select our package from:


C:\Program Files (x86)\Microsoft Visual Studio Tools for Unity\2013\

Alternatively, if you have the Administrator rights on your machine you can copy the package to:


C:\Program Files\Unity\Editor\Standard Assets\

And you'll find it in the Import Package menu next time you need it.

File Opening


To properly open your scripts from Unity, you need to change the External Editor to our file opener.

In Unity, go to the menu Edit -> Preferences, and in the External Tools tab, change the file opener to:


C:\Program Files (x86)\Microsoft Visual Studio Tools for Unity\2013\UnityVS.OpenFile.exe



Known issue


Unity 5 changed the path to the tool named pdb2mdb that we're using to convert .NET debug symbols to the Mono debug symbols that Unity understands. You need to invoke the tool yourself on your dll and pdb files if you want to debug custom dll files.

Run the command:


C:\>"C:\Program Files\Unity\Editor\Data\MonoBleedingEdge\bin\cli.bat" "C:\Program Files\Unity\Editor\Data\MonoBleedingEdge\lib\mono\4.5\pdb2mdb.exe" Path\To\MyCustomAssembly.dll

Replace Path\To\MyCustomAssembly.dll by the actual path to your dll file (the .pdb needs to be located in the same folder), and this will generate a mdb file. Just copy the dll and the mdb file in the Assets folder and you'll be able to debug the code from Visual Studio.

12 Nov 2014

permalink

Today we release a preview of the Visual Studio Tools for Unity 2.0.

The 2.0 Tools for Unity will bring many new features and bug fixes, and this preview is the opportunity to share the features and fixes that are already completed.

The 2.0 Preview Tools for Unity release, among other features, adds support for the Visual Studio 2015 Preview, and enhances the debugging experience. Please refer to our ChangeLog for the complete list of features and bug fixes.

Thanks to everyone who submitted suggestions to the Tools for Unity's UserVoice. We're happy to report that one of the most voted suggestion, adding Code Coloration for Unity's shaders in Visual Studio has been implemented and is available for the Visual Studio 2015 Preview.

You can update the Tools for Unity directly from the Visual Studio Extensions manager, or by installing them from the Visual Studio Gallery:

09 Oct 2014

permalink

Today we release the Visual Studio Tools for Unity 1.9.2, our second bug fix release for the 1.9 series.

We would like to use this opportunity to thank everyone who reported bugs through Microsoft Connect and who helped us diagnose those issues. Please see our ChangeLog for a complete list of the changes.

You can update the Tools for Unity directly from the Visual Studio Extensions manager, or by installing them from the Visual Studio Gallery:

22 Sep 2014

permalink

As announced on the Visual Studio blog, today we release the Visual Studio Tools for Unity 1.9.1, a bug fix release for the 1.9 series.

This release fixes most of the issues reported on the Visual Studio Connect site. We've also used this opportunity to add new features to improve the integration with Unity, such as automatically renaming or deleting Unity's meta files when manipulating files from Visual Studio. For a complete list of the changes, please see our ChangeLog.

You can update the Tools for Unity directly from the Visual Studio Extensions manager, or by installing them directly from the Visual Studio Gallery:

29 Jul 2014

permalink

The team is proud to announce the 1.9 release of Visual Studio Tools for Unity, formerly known as UnityVS, our fist release since we've been acquired by Microsoft.

Please see the annoucement on the Visual Studio blog. To know exactly what changed, you can go directly to the ChangeLog.

Visual Studio Tools for Unity is now directly available from the Visual Studio Gallery, for each of the Visual Studio version we support:

UnityVS 1.8 to VSTU 1.9 migration

If you are migrating an existing UnityVS 1.8 solution, we recommend that you:

  • Delete the UnityVS .sln and .*proj files from the root folder of your Unity project.
  • Import the new Visual Studio Tools for Unity package into your Unity project as shown in the documentation.
Your new solution will be automatically generated.


Copyright © 2011-2014 SyntaxTree. All rights reserved.

Unity is a registered trademark of Unity Technologies.
Visual Studio is a registered trademark of Microsoft Corporation.