This is the recommended way to set up Visual Studio for debugging with Unity. NET assemblies created with tools like Visual Studio) and Native plug-ins (platform-specific native code libraries). There are two kinds of plug-ins you can use in Unity: Managed plug-ins (managed.

The Unity Editor installer includes an option to install Visual Studio with the Visual Studio Tools for Unity plug-in A set of code created outside of Unity that creates functionality in Unity. Configure the code editor Visual Studio (Windows) Universal Windows Platform, however, supports only two. Unity supports three different scripting backends depending on target platform: Mono. More info See in Glossary scripting backends A framework that powers scripting in Unity. More info See in Glossary and IL2CPP A Unity-developed scripting back-end which you can use as an alternative to Mono when building projects for some platforms. It works with both the Mono A scripting backend used in Unity. The Unity WebGL build option allows Unity to publish content as JavaScript programs which use HTML5 technologies and the WebGL rendering API to run Unity content in a web browser. Managed code debugging in Unity works on all platforms except WebGL A JavaScript API that renders 2D and 3D graphics in a web browser. You can attach these code editors to the Unity Editor or Unity Player to debug your code.

Visual Studio (with the Visual Studio Tools for Unity plug-in)Īlthough these code editors vary slightly in the debugging features they support, they all provide basic functionality such as break points, single stepping, and variable inspection.

Unity supports the following code editors to debug C# code: You can use a debugger to inspect your source code while your application is running.

Setup visual studio for unity