Visual Studio 2013 Tools for Unity

Microsoft Free

Write and debug your Unity 3D games inside Microsoft Visual Studio.

(40) Review
Visual Studio
Download (46,661)
E-mail Twitter Digg Facebook
Add to favorites
Reviews (40)
Q and A (28)
Sign in to write a review
Sort by:

by ferti | September 24 2014

The last version seems to work very well compared to the previous. I had no Unity freezes anymore since I installed it. Thanks for the fix !

by ollydbg | September 21 2014

vs tools for unity is pretty good.But there is a Bug:
with vs tools for unity,asynchronous socket callbacks do not work.
please fix this bug.
it waste me a lot of time.

Sebastien Lebreton September 22 2014
| Edit |

Yes it is a bug on Unity3D side (so that you should also reproduce your issue with MonoDevelop). Hopefully this is now fixed, you just have to wait for their fixed release.

Check this:

by Freddedonna | September 17 2014

Didn't have any issues with the extension itself yet, but it reset ALL my VS settings (language, color, etc) upon installation.

Sebastien Lebreton September 19 2014
| Edit |

Sounds very strange, we only rebuild extension cache during install.Please Open an issue on Connect so that we can investigate.

by sebi86 | September 11 2014

As already mentioned in previous comments, version 1.9.0 has serious debugging issues. Unity crashes after a changed script is attached to Unity. When can the upcoming version 1.9.1 be expected?

Sebastien Lebreton September 22 2014
| Edit |

I do not have an exact date to give, but it should be very soon.

EDIT: 1.9.1 is available

by Ocean68 Studio | September 04 2014

Version 1.9.0 works well with Unity 4.5.2 but it is impossible to debug with Unity 4.5.3
Hopefully get an update soon.

This tool is great!!!

by Dave Voyles - MSFT | August 31 2014

Thank goodness it's finally free!

by thormond | August 27 2014

It has one severe bug: if you do some changes in your code, do Ctrl+S and then press "Attach to Unity" before alt tabbing to Unity first and waiting for the compiler spinner to finish - it will crash the Unity process (very annoying when debugging something in Start() or Awake() since you have to launch debugger before hitting play button), can we expect some fix so it either prevents you from hitting "Attach to Unity" or initiates compilation process and waits for it to finish? (preferably the second option)

Sebastien Lebreton September 15 2014
| Edit |

This is fixed in the upcoming 1.9.1 release.

by antonov.3d | August 20 2014

Have VS2013 Express and unity4.5.2
upon installing/reinstalling im getting
"VS not found", what i should do?

Sebastien Lebreton August 21 2014
| Edit |

VSTU does not support VS Express edition

by bernieman | August 18 2014

I am changing my rating from 1 to 5. I'm sorry about the rant below. The issue I was having was due to the fact that I had missed a step in the VSTU 1.9 migration. I forgot to import the Visual Studio 2013 tools asset.

My apologies. Hopefully this post may help the next guy who may have missed the same step.

========== original post =============
I followed the steps suggested in description, UnityVS 1.8 to VSTU 1.9 migration.
I removed all .*proj and *.sln files and started Unity after that.

But its does'nt work. Two project keep failing

I also tried using the function Generate project files. No luck.

The visual Studio migration report contains two errors, in both cases the error is :
"The application which this project type is based on was not found."

I'd love to give this product a higher rating since I love the idea of a troublefree seamless integration between Unity and Visual Studio. But that's not the way it looks at the moment.

by tgraupmann | August 12 2014

Unfortunately, after I installed the latest, it made it not possible to open projects in VS 2013 Pro. After uninstalling I could open VS 2013 projects again. The previous UnityVS installers worked fine.

The extension cache seems to take a while for the installer, and it appears to cause instability.

Sebastien Lebreton August 19 2014
| Edit |

We fixed this issue in the upcoming 1.9.1 installer. It seems that the installation failed to recreate the Visual Studio extension cache. We saw this happen if there was a stray devenv.exe process.

Try to do this:
- Make sure that you do not have any Visual Studio instance running
- Properly remove VSTU 2013, using Control Panel, Programs and Features
- Reinstall VSTU 2013

If you still encounter issues, repair your Visual Studio Installation using Control Panel, Programs and Features: Microsoft Visual Studio 2013, Modify, Repair. Then if you haven't yet upgraded to Update 3, you should try to.


by plonkman | August 11 2014

Good tool.

Works pretty well, although, as another reviewer has mentioned, Unity will hang (not responding) quite a lot when VS is connecting.

I have to add that I'm not particularly happy that I'd bought this just before it went "free" though.

I like this tool, but I have to give it 1 star for the hanging on connection.

Sebastien Lebreton August 19 2014
| Edit |

We fixed a handshake timeout issue between Unity in VSTU in the upcoming 1.9.1 release. It should fix this.


by Trojan.Rn | August 11 2014

it works well on vs2013

by Justin Cho | August 09 2014

It is for VS 2012

by Twilek | August 07 2014

The 1.8.2 is worked, the 1.9.0 not working ..
When i try to attach to unity process the unity still working (not responding) 9 out of 10 times.

Please reopen the 1.8.2 download link.

Nice name, nice icons :) but please switch back the oldest version thanks!

Sebastien Lebreton August 19 2014
| Edit |

We fixed a handshake timeout issue between Unity in VSTU in the upcoming 1.9.1 release. It should fix this.


by Zyxil | August 05 2014

Unity debugging "just works". There are a few bits that don't work as advertised, but nothing that causes any heartache.

by Aevir | August 02 2014

An excellent tool, highly recommended for Unity developers.

by East Ash | August 01 2014


by Wendelin Reich | July 31 2014

Ahh... the intermediate window works!

by ahersee | July 31 2014

This paid for it's self in saved time when it was formally sold as UnityVS, a great buy. Now it's free from Microsoft everyone should give it a go. I develop on a Mac but now run Unity in a virtual machine just so that I can use Visual Studio and this plugin. Absolutely fantastic!

I must spend some time to work out if there's a way to setup the project on a shared drive so I can run Unity native on the Mac and visual studio in the VM.... or hopefully there's a guide somewhere for such a setup.

by Jamie Hales | July 30 2014

Absolutely fantastic, loving the new additions/bugfixes, seems much much more stable now!

1 - 20 of 40 Items   
Sign in to start a discussion

  • Not installing
    3 Posts | Last post Tue 6:47 PM
    • I have Visual Studio 2013 Update 3, Installed this package and appears as installed in the Extension and Updates menu, but the package file is not added to the Standard Packages folder in the Unity installation folder and I don't see a UnityVS drop down menu in the Visual Studio IDE.
    • Hello! So I had this issue too. What I found is that I was using Unity 4.5.2 for my current project even though I had Unity 4.5.4 installed. UnityVS was removed from Unity 4.5.2 and added to Unity 4.5.4 even though that's not the version our team is currently using.
      If this is the case, you can go to Program Files (x86)/NewestUnityDirectory/Editor/Standard Packages and copy the unityPackage file over.
    • The problem was that I have Unity 5 beta, the path has dots:
      C:\Program Files\Unity 5.0.0b1
      Maybe that is the problem.
      I solved the issue with these steps:
      1) Installed Unity 4.5 (current non beta version) and then installed Unity Visual Studio Tools 2013 
      2) The unitypackage was created in the Unity 4.5 "Standard Packages" folder, I've made a backup of it.
      3) Installed Unity 5 beta again and copied the unitypackage in the "Standard Packages" folder of the Unity 5 folder.
  • Getting the 2012 version?
    9 Posts | Last post Mon 8:42 PM
    • Something weirdi s happening. I download the file, the installer is called "Visual Studio 2013...", but when I install, it installs the visual studio 2012 version, and of course it doesn't work...
      MS uploaded the wrong file? Anyone else getting this?
    • The same is happening to me
    • The same is happening to me
    • The same is happening to me
    • The same is happening to me
    • There is hardly any doubt that the file is the correct one. I tried to download and install it on several VMs with 2013 only, 2012+2013, 2010+2012+2013 and it always installed in the correct Visual Studio 2013.
      So what do you exactly mean by "it installs the visual studio 2012 version" ? If VS 2012 is opening your projects from Unity, please make sure that you correctly imported the Visual Studio 2013 Tool for Unity from Assets\Import package menu for all your Unity projects.
      Also check that in VS, from Help\About Visual Studio menu or from extension manager you can see that VSTU is installed.
      You can try to uninstall VSTU, repair your VS installation then re-install.
    • I had 2012 version installed and then installed the 2013, I thought that the version installed with the 2013 package was 2012, but that was the version I already had. So the real problem is that the 2013 version was not installed at all after running the 2013 installer.
    • Check this page:
      If you still cannot install VSTU, please open an issue on Connect so that we can track and investigate this.
    • The problem was that I have Unity 5 beta, the path has dots:
      C:\Program Files\Unity 5.0.0b1
      Maybe that is the problem.
      I solved the issue with these steps:
      1) Installed Unity 4.5 (current non beta version) and then installed Unity Visual Studio Tools 2013 
      2) The unitypackage was created in the Unity 4.5 "Standard Packages" folder, I've made a backup of it.
      3) Installed Unity 5 beta again and copied the unitypackage in the "Standard Packages" folder of the Unity 5 folder.
  • Unsupported
    2 Posts | Last post Sun 2:41 PM
    • Hi,
      When I try to open any script from Unity, I get the "unsupported" message :
      This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them. 
      For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.
      I don't know what to do to solve this issue, so any help would be very welcome. (and sorry if this is a noob question...)
    • OK, problem solved. I had to remove and reinstall UnityVS, repair did not do anything.
  • Constantly crashing
    3 Posts | Last post Thu 8:48 PM
    • I am crashing every single time I try and debug now with 1.9.1. If I set a breakpoint, Unity crashes every single time I hit it. This didn't happen in 1.9.0. To upgrade, I installed this latest version, then went into Unity and deleted my previous UnityVS assets. Saved/quit/restarted Unity, re-added the UnityVS asset. Saved/quit/restarted. It's a 100% repro rate. Using Unity 4.6 beta 17 and VS 2013 on a Win7 x64 machine.
    • Hi,
      Sorry to hear that you're running into troubles. We've heard of a similar case that had an easy work around:
      Can you delete all UnityVS* files (*.suo, *.csproj, *.sln) from the root folder of your Unity project, and recreate them from Unity (using the menu Visual Studio Tools -> Generate Project Files) ? Hopefully that should fix it.
    • That seemed to work. Thanks!
  • "key not valid is specified state"
    2 Posts | Last post September 23, 2014
    • I have set Visual Studio 2013 Professional as my default development environment for my Unity 3D project.  I'm trying to install Visual Studio Tools for Unity so that I can debug properly... however every time I try to install I get
      "key not valid is specified state"
      There is no log that I can find and no additional information.  I've been looking on the internet for several hours, but all the solutions for this problem are related to TFS; not Tools for Unity.
    • Hi Jason, you can try to repair your VS installation prior from installing VSTU (from Programs and Features). 
      If you still cannot install VSTU, please open an issue on Connect so that we can track and investigate this.
  • Update procedures
    2 Posts | Last post September 22, 2014
    • With the update to 1.9.1, what is the proper procedure to update? Running the update in VS will update plugin, but do I then need to upgrade the Unity package file in all my projects?
    • Hi,
      VSTU will try to upgrade the Visual Studio Tools package, but yes, it' s a good idea to make sure it's ugraded (by importing it like the first time you did).
  • Breakpoints no longer working in Unity 4.60b17?
    2 Posts | Last post September 22, 2014
    • UnityVS ( worked great with Unity 4.5, but after upgrading to Unity 4.6, breakpoints are no longer working?
      Any idea/suggestion how to resolve this?
      Debugging in VS was one of the features I liked most about UnityVS
    • Upcoming 1.9.1 will work as expected with stable 4.x and 4.6 beta
  • Open file from Unity
    2 Posts | Last post September 22, 2014
    • Slight bug in UnityVS, it's not a showstopper but a tad annoying nonetheless.
      If I create a new script file from Unity (or do anything on the Unity side that forces a recompile), and then double-click to open the file in VS, it will first open the file, then detect that the project has been modified and wants me to reopen it, then afterwards the file I just opened becomes sort of... weird. As if it doesn't think the file is actually part of the solution (making any edits will display the full filepath in the file tab, and sometimes it will constantly show an asterisk in the title even when saving, as if there are unsaved changes to the file).
    • Please Open an issue on Connect so that we can track and investigate this.
  • Connect to Unity from a VM
    4 Posts | Last post September 19, 2014
    • I am attempting a setup that I think is not atypical for Unity developers: connecting the Mac version of Unity (4.5) to Visual Studio Ultimate running in a Parallels virtual machine. I believe people had some success with this configuration using the old SourceTree plugin, but I am not having much luck. Specifically, I can get the plugin to:
      • See my Unity instance
      • Start debugging against my Unity instance (F5, connection bar turns orange)
      However, as soon as I start the game in my Unity editor:
      • Only one or two log statements make it to the Visual Studio console (the exact number is unpredictable)
      • Breakpoints never trigger
      • I usually see multiple thread disconnection messages appear immediately in the console ("The thread 0x[Address] has exited with code 0 (0x0)").
      Note that the plugin does not ever explicitly disconnect from Unity (bar remains orange); practically, though, it appears to lose the connection as soon as the game starts up.
      Could the developer please comment on this? Even a clear statement that this VM setup -- which I know was considered at least experimentally supported by Syntax Tree -- is no longer expected to work would be helpful.  More optimistically though, since this configuration is one that I'm sure many Unity devs with iOS projects would love to use, if there is any way that it can be made to work that would be awesome.
      Thanks very much.
    • +bump.
      I have the same exact issue and configuration. I primarily develop on the Mac for iOS support. If this configuration could be made to work correctly it would be fantastic!
    • I was able to get it to work!
      After trying several different things I found that in Parallels instead of opening the solution from the "Home" network mapped drive I actually used the "Mac Disk" drive which Parallels mounts. This drive is not a mapped network location but instead appears as a physically connected drive. I'm running Windows 7 with Parallels Desktop 10.0.2.
      I don't know why this would make a difference (it certainly doesn't seem to have changed the loaded modules) but it does cause the breakpoints to hit. 
      I will, however, note that for the console logging I also noticed that if the Log statement doesn't change then it will only be recorded once in the VS console. I added a Random.Range(0F,100F) to the log statement and this caused it to be output consistently.
      Hope this helps!
    • We still consider this as an experimental support. We fixed a lot of issues regarding debugger connection and breakpoints binding. We made several tests with Unity 4.5.4 (4.5.x releases contains some important bug fixes about debugging) and all is working as expected with a Mac and the upcoming 1.9.1 release.
  • Default namespace?
    5 Posts | Last post September 12, 2014
    • Is there a way to prevent Unity from clearing the Default namespace field found in the Project Menu -> [ProjectName] Properties...?
    • Looking at the UnityVS.Unity.CSharp.csproj, this keeps getting stripped out.
    • Hi Garth,
      You can interact with how Visual Studio Tools for Unity generates project files by using the Unity style callback ProjectFileGeneration.
      Have a look here:
    • Thanks for the link! For anyone else who finds this message, here's the two lines I added to the link provided by Sebastien.
      XElement namespaceElement = document.Descendants("{}RootNamespace").Single();
      namespaceElement.Value = "TicToc.ProductName";
    • Thanks for the example Garth!
      also place the ProjectFileHook.cs in an "Editor" subdirectory
1 - 10 of 28 Items