Visual Studio 2013 Tools for Unity

Microsoft Free

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

(76) Review
Visual Studio
Download (168,066)
E-mail Twitter Digg Facebook
Add to favorites
Reviews (76)
Q and A (128)
Sign in to write a review
Sort by:

by formulahendry | April 23 2015

by Protostar Dean | April 21 2015

Great Tool!
However since getting this latest update Unity seems to be crashing very frequently when I am attached.

by 金奇 | April 18 2015

very good

by Bakinovski | April 16 2015

While I am debuging I can't see exceptions in debuger.
For example in such source code I can't see object exception at line with Debug.Log
throw new Exception("test exeption");
catch (Exception exception)
UnityEngine.Debug.Log("Test exeption was thrown!");
Do you have the same issue? If it is bug do you plan to fix it?

P.S. Tool is realy grate - thanks for it.

Sebastien Lebreton April 20 2015
| Edit |


Yes, at this time, the exception object is not properly added to the debugging context so that you will not be able to inspect it using Watch window.

We will add support for that in the final release of VSTU 2.0.


by Kuato4 | April 13 2015

by QuYong | April 11 2015

very useful tools for Unity game developing, forget about the MonoDevelop

by KingRecycle | April 11 2015

New version doesn't work for 32-bit so I can't use it anymore. Please fix this.

But other than that it's better than using anything else in my opinion.

Sebastien Lebreton April 11 2015
| Edit |


We have just re-uploaded a new installer with proper x86 support.
Can you please download the file again and try to install it ?

Sebastien Lebreton [MSFT]

by CodePiao | April 07 2015

Very Cool .

Use VS 2013, coding for Game。

by AByrd | April 06 2015

A few issues with

Output is now spamming "The thread 0x<stuff> has exited with code 0" at a rate of about 2 per second.

The Error List now flickers open and closed frequently.

Sebastien Lebreton April 09 2015
| Edit |


When debugging, we've always notified what's happening in the output window, including thread creation and death.

You can configure VSTU to not send the Unity console to VS this will avoid the flicker you're seeing. You can do it from Unity, in the menu Visual Studio Tools -> Configuration and uncheck Send Console to Visual Studio.

by nu Assets | March 30 2015

Although the system has some minor bugs, it's probably one of the mightiest add-on you can get for Unity 3D. The integration is 99.9% seamless and its usability is pretty nice. If you're used to work with VS - you probably are as a professional - there's no way around it!

Well done!

by CoRuMmo | March 10 2015

Cannot come back to mono develop. I can't simply stand its interface anymore.
Long life Visual Studio tools for Unity!
Many thanks for this must-have tool.

by AdamNash_FM | March 03 2015

by Yatajga | February 20 2015

by Chad Keating | February 19 2015

by Mosy.Galaar | February 17 2015

I absolutely love this extension. It is a must for any Unity Project that
you are using Visual Studio to code.

My only real complaints are that it is not working properly with Unity
for Console game development, and that every time I get a new version of
Unity I have to reinstall it. The first should be fixed, the other is a
problem with Unity and not solvable by the dev team.

by chall3ng3r | February 06 2015

I started off my Unity development with 4.2 with MonoDevelop on Windows, it was okay. But I missed the awesomeness of Visual Studio. I tried this toolkit before MS bought them, it wasn't quite polished, but after MS bought it, its been really great.

I really like intelli-sense and refactoring and debugging features UTVS provides. Anyone starting with Unity on Windows, I would highly recommend to use this toolkit, it makes things a lot easier and fun.

There's one suggestion:
Please publish the UTVS extension on Unity's Assets Store, rather than copying it in Unity's install folder. When I update Unity, it removes the extension as well, so I have to manually copy it in Unity folder.

When UTVS is installed via Assets Store, it will be kept in Windows user profile, separate from Unity install folder, and also I can update it from within Unity.

Sebastien Lebreton February 11 2015
| Edit |

Thanks, yes we are thinking of something more streamlined for our package. Stay tuned !

by borso1 | February 01 2015

There's a bug with the "Create script method" command. When you insert the OnRenderImage function, it swaps the order of its parameters.
This is the one it creates:
"public void OnRenderImage(RenderTexture destination, RenderTexture source)"
while this is the correct one actually:
"public void OnRenderImage(RenderTexture source, RenderTexture destination)"

Sebastien Lebreton February 02 2015
| Edit |


Yes, this bug was already fixed but the fix is not yet released. It will be available for the next VSTU release.


by Jashan Chittesh | January 27 2015

It's really nice that this exists - I actually bought UnityVS a while back ... but eventually stopped using it because it didn't add as much benefit for me as it caused trouble.

Unfortunately, it seems that this hasn't changed much: Since installing the package to my Unity 4.6.1 project about half an hour ago, Unity crashed two times: It just stopped working in the middle of compilation.

I haven't seen the crashes in Visual Studio that made me stop using it back then (this was rather nasty because it prevented files from being saved and it took a while until you'd actually notice that this was happening sometimes resulting in data loss). Those were very sporadic, so we'll see if those return (I had bug reports filed so maybe those are actually fixed).

Also, it's kind of sad that UnityScript and Boo are no longer supported. I'm not using those much but it was actually the most important feature for me that UnityVS brought.

So, I hope you keep on developing and improving this. Btw, I'm using Unity on the Mac side and VS in VMWare Fusion - so that part of the integration is really important for me!

by Bjark | January 22 2015

I cannot belive how shit this STILL is...
I've given this a try 5 times or so for the past two years, each time thinking "maybe now it has become more stable". This does NOT work well enough yet, and is completly unuseable in my opinion.

It sometimes breaks inside a "if (false)" scenarios.
It sometimes completly skips lines of code.
It crashes unity randomly when simply stepping through your code.
It crashes visual studio
The Immidiate or Watch window doesnt work well, and can crash evrything if you inspect the wrong thing.
You cannot break on certain lines (you can set a breakpoint, but it will completly ignore it, properbly because unity is smart and optimizes your code. but still, then don't optimize my code when i'm debugging for god sake!)

I mean, the amount of time i have spent simply because the debugger was showing me the wrong values under inspection... It takes up more time than you gain if you had debugging ... And thats alot!

Not recommended!

Sebastien Lebreton January 22 2015
| Edit |


Thanks for taking the time to write a review!

I'm sorry to hear that you've had a poor experience with this tool: that's definitely not the experience we're aiming for :)

We're aware that the old Mono version that Unity ships makes the debugging experience bumpy sometimes, but definitely not to the extent where it's not usable.

Which makes me wonder if there's not a more complex issue with your setup at play here.

I'd love to discuss the issues you're having and how we can address them. Please feel free to reach out: vstusp at microsoft dot com.

Thanks & best regards,
Jb Evain, Dev lead, VSTU

by kaz2057 | January 13 2015

Hi Sebastian,

I loaded UnityVS 1.9.8 with VS13 in Unity5 b18 but when I double click on any files in the project, VS13 doesn't load my files.

Then, solution explorer into VS13 doesn't found any files ...

Any suggest?

Sebastien Lebreton January 13 2015
| Edit |


Double check that you properly imported VSTU package in your Unity project.

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

  • System.* references in project
    1 Posts | Last post Thu 6:52 PM
    • Hello,
      I'm using VS2013, Unity 5.0.2, Tools v1.9.8. 
      Noticing that references to System.Core, System.XML and System.Xml.Linq are automatically included in the project even though those libraries are not used at all in the project.
      I believe Unity then packages these DLLs in the final build as well which adds unnecessary size to the player. 
      Is this intentional? Is there a way to permanently remove these unused references?
  • File names converted to lower case
    2 Posts | Last post Mon 8:37 AM
    • Hi,
      I'm using VS2013 via Parallels, Unity 5.0.1p1 and Tools version 1.9.9. Sometimes, for reasons I can't figure out, the file names get renamed as lowercase whenI save - e.g. MyClass.cs to myclass.cs. This of course causes issue in Unity. I can force the file to save as camel case by simply saving the file again. Oddly, the file name in VS doesn't appear to change. I can't be sure.
      Looks like there have been problems with Unity doing this in the past, but nothing I could find recently. Any thoughts?
    • Hello,
      Do you hit this issue every-time or randomly ? If you are able to find a way to easily reproduce it would be great.
      Sebastien Lebreton [MSFT]
  • Cannot debug with unity 5
    3 Posts | Last post May 13, 2015
    • I put a breakpoint in vs, try attach to unity from vs, running the game.I got message from unity console in vs but the breakpoint doesnt fire? I use 1.9.9 of tool, vs 2013 ultimate, unity 5.0.0b1. How can I fix this problem? 
      Thank you,
    • Hello 
      The first thing you can try is to upgrade your Unity beta version to a final one like 5.0.1f. 
      Then be sure to properly setup Firewall exclusions for Visual Studio and Unity so that VS can connect to the Unity debugging layer when attaching.
      Sebastien Lebreton [MSFT]
    • Thanks Sebastien,
      I will try your solution and feedback asap.
  • does 1.9.9 address mac stability issues?
    3 Posts | Last post May 11, 2015
    • Hi JB, 
      does the new build work better with unity on the mac?
    • Hey,
      In 1.9.9 we fixed a code path that could trigger a Unity freeze on OSX when reloading the game. I suggest you give it a try :)
      Jb Evain, Dev Lead, Tools for Unity
    • I have been running the latest all weekend and so far zero crashes.
      now, I am just using vs to edit code, I am not debugging but maybe I will be brave enough to build and debug from vs later this week.
      great job, it's so helpful to have this working.
  • Migration Report
    3 Posts | Last post May 11, 2015
    • Visual studio for unity tool isn't working.When i open a script, Just I see a null visual studio window. I use Unity 5.0.0f4, visual studio 2013 professional and win8.1 . I installed unityvs for vs2013 and it gives this error to me.I installed .net framework 3.5.
      It gives that report
      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.
      	 - UnityVS.New Unity Project.CSharp, "C:\Users\chef\Desktop\New folder\New Unity Project\UnityVS.New Unity Project.CSharp.csproj"
      No changes required
      These projects can be opened in Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1 without changing them.
      	 - UnityVS.New Unity Project, "C:\Users\chef\Desktop\New folder\New Unity Project\UnityVS.New Unity Project.sln""
      Please help me.I really want to use this tool.
    • Hello,
      The extension do not seems to be properly installed.
      You can try to uninstall then reinstall VSTU again. You can also try to repair Visual Studio and to install latest VS Updates.
      Sebastien Lebreton [MSFT]
    • reinstall VSTU and .net framework 4.5.2 update fixed the problem.thank you very much.
  • Where can I download the old versions?
    1 Posts | Last post May 08, 2015
    • I unfortunately deleted the MSI file of 1.9.8 in the WinSXS folder. Now when I try to upgrade to 1.9.9, it prompts that the old MSI file is need to uninstall previous version.
      Could any one tell me where to download the old MSI install files?
  • Console (Collapse)
    3 Posts | Last post May 06, 2015
    • Hello, I start using this plugin for a few days and I see the console on VS is behaving like the unity console with the Collapse button toggled.
      To be easy to reproduce, print a few lines on the console, like this:
      You will see on the "console" (error list) only:
      The 2nd "Hello1" don't show up on the error list (because it's a duplicate).
      So, my question is, this behavior can be changed in Unity or Visual Studio?
    • Hello Rafael,
      At this time this behavior cannot be changed, we are removing duplicates on the VSTU side. 
      Sebastien Lebreton [MSFT]
    • Hi Sebastien, thanks for your reply.
      I will be waiting for changes on this behavior...
  • unity tools for visual studio 2013 Problem
    1 Posts | Last post May 04, 2015
    • I have recently updated my Visual Studio 2013 Ultimate and now each time I double click in Unity editor on script it launches a new Visual Studio Instance. I have tried everything, cleaning up all caches, reinstalling Unity, etc. but eventually the problem remains. Maybe someone can have a clue why is this happening.
  • 2.0 preview?
    2 Posts | Last post May 04, 2015
    • The description says "Visual Studio Tools for Unity 2.0 Preview 2" but where I can download it?? 
      The download button only brings 1.9.9 and the VS 2013 nuget only gives me 1.9.8. 
      Where to get the 2.0  preview??? 
    • Hello,
      1.9.9 is our technical version for "Visual Studio Tools for Unity 2.0 Preview 2", 1.9.8 was for Preview 1. We will use 2.0 for the final version.
      So what you can download here is always the most up-to-date.
      (I've also checked the VS 2013 Extensions and Updates window, and the proper version is provided).
      Sebastien Lebreton [MSFT]
  • no documentation at all
    3 Posts | Last post April 29, 2015
    • with the UnityVS*.sln generated file i got zero descriptions of what functions or methods from a class do.
      For example:
      List<int> list= new List<int>();
      int elem=list.Count;
      .Count dont show any information of this property at all.
      for known methods like the one above there is no problem , but i like to see the description of all methods like it does always in the normal sln proyects generated in visual studio.
      Visual Studio 2013 community.
      VsTools 1.9.8.
      Same problem with visual studio 2010 & vs tools 1.9.8.
      If i open just the script.cs that i want to see from my  windows explorer in visual studion, it works perfect as always.
      Pls fix this. Other way is almost the same write my code in the notepad++
    • oh i forgot in mono develop it show the methods descriptions. I dont understand what happens but it's annoying as hell dont have method descriptions in visual studio
    • Can you try with our latest release? Do you experience the same issue if you disable documentation generation in Visual Studio settings/Tools for Unity ? (And removing all generated xml files from your project) ?
      Sebastien Lebreton [MSFT]
1 - 10 of 128 Items