whopaster.blogg.se - Debugging unity3d visual studio tools for unity community

DEBUGGING UNITY3D VISUAL STUDIO TOOLS FOR UNITY COMMUNITY INSTALL
DEBUGGING UNITY3D VISUAL STUDIO TOOLS FOR UNITY COMMUNITY WINDOWS

What is not documented are the small things you need to do next:

DEBUGGING UNITY3D VISUAL STUDIO TOOLS FOR UNITY COMMUNITY INSTALL

Basically you install the product itself, the C# for Visual Studio Code tools and the Debugger for Unity and you are all set. The process for setting it up is actually nicely documented at this page and does not involve a lot of work. I am actually going to give it a go, although for a lot of things I will probably fall back to Visual Studio 2019. You can actually use Visual Studio Code as your Unity External Script Editor if you like.

It’s not as fast as Visual Studio Code but at hell of a lot faster than it used to be when Visual Studio 2019 was selected as editor in Unity. Adding a C# file from Visual Studio will make Unity hiccup for a few seconds, then resume. Adding files in the Unity Editor will only make one project reload. sln file, it will just open the generated solution with all it’s projects as always. If you open Visual Studio 2019 by clicking the. csproj files, although Visual Studio Code does not seem to use them. Unity, for some reason, still creates the. Yeah, me too, and now comes the crazy part. You will also notice adding files, both in Visual Studio Code and in Unity, will take mere seconds. If you now double-click a script in Unity, it will open Visual Studio Code in stead of Visual Studio 2019. Then, open Unity, select Edit/Preferences, hit “External tools” and from the drop down “External Script Editor” select “Visual Studio Code”. But please hear me out and go ahead, install Visual Studio Code. I have lived in it for a little short of two decades. Wait! Read on! Yes, I am partial to Visual Studio as well. I presume it works, but when you often need to test and deploy on a device (like me), you will need to change configuration often and this in itself will take time - and it will make the deploy to a device yet even longer than it already is. The first solution has been suggested to me by Edd Smith. Set Visual Studio Code to be your External Script Editor.

DEBUGGING UNITY3D VISUAL STUDIO TOOLS FOR UNITY COMMUNITY WINDOWS

Change the project setting to Windows Standalone, and only change it back when you need to build on a device.

It’s maddening.īut there are ways to get around it. And all the while it’s doing that both Unity and Visual Studio itself are not responsive. Visual Studio asks you to reload the project, all 99 (or 101, depending on your settings) are unloaded and reloaded, you might even get some errors as extra.

You might wait well over 15 seconds, especially with scripts. This has an unintended and very unwanted side effect: adding files to your solution becomes slow. Solution: Visual Studio 2019 and Unity 2019.4.x LTS are very slow when adding/changing filesĪlthough I like to stay at the minimum recommended version for the MRTK (currently 2018.4.20f1), for the app we are currently developing for my employer we need to target ARM64 and for that you need 2019.4.8f1 (until short, the latest LTS).