Unity extension for Visual Studio Code – Now Generally Available

Jb Evain

Today, we are thrilled to announce the general availability of the Unity extension for Visual Studio. This extension, built upon the C# Dev Kit and C# extensions, gives you a comprehensive toolkit for your Unity development in Visual Studio Code across Windows, macOS, and Linux.

We shipped the first preview of the Unity extension for Visual Studio Code last year and have been working since on improving the experience thanks to your feedback!

Unity and the Unity extension for Visual Studio Code

What is the Unity extension?

Code Editing powered by Roslyn

C# editing is backed by the C# extension, giving you powerful IntelliSense code-completion. Along with the IntelliCode for C# Dev Kit extension, you get AI-assisted features such as whole-line completions and starred suggestions as you type.

The extension also includes the Unity Roslyn Analyzers project, giving you suggestions and code fixes tailored to Unity.

Unity Roslyn analyzers suggesting a code fix

Debug Unity and your Unity games

The extension makes it easy to debug your Unity games, either running in the Unity Editor or standalone, while running on all the platforms that Unity support. Just press F5 to attach the debugger to your game running in the Unity Editor or use the new “Attach Unity Debugger” command to see a list of Unity Editors and Unity Players that you can debug.

Attach Unity Debugger command

After that, just put a breakpoint in your code and run your game in Unity!

Debugging Unity with the Unity extension

How to get started?

Head over to the Unity extension page for a complete README on how to get started, depending on the version of Unity you are using.

What is next?

Today’s official launch is only the start as we will continue to listen to your feedback and work toward improved performance, reliability, and adding features to support your Unity development in VS Code.

Please share your feedback by reporting new issues via VS Code or searching the existing enhancement and issues and give your ‘thumbs up’ or additional context to the issue to help us prioritize.


Discussion is closed. Login to edit/delete existing comments.

  • Vincent Wang 0


    I am learning Unity on windows. Currently I’m using Visual Studio as the editor and debugger. Is there a particular good reason to switch to VS Code on windows?

    • Jb EvainMicrosoft employee 1

      Hi Vincent,

      Both tools are extremely capable, but they also have a different approach on many things. Visual Studio is a full fledged and fully featured IDE. Visual Studio Code is more lightweight and focuses on text based commands and scenarios. Visual Studio provides a great IDE experience for Unity, and I personally use both tools, so I’d just suggest to use whatever makes sense for you.

  • hifron 0

    1.) What do you think about Unity Auto Compilation from VS Code extension for VS Code?

    2.) I also think that syntax for methods like:
    private void Start() {

    is better for saving display space and easier to read longer code than
    private void Start()

    3.) but that is the decision for C# but not mine and I think it should be otherwise for good programmer habits.
    4.) Unity GUI is somehow connected with onMouseDown former GUI but automatically is its Editor Tools not made CSS ready and A New World emerging when it could only CSS style be edited by UI Toolkit and designed in its former Unity GUI…
    5.) Unity is somehow heavy weight like VS Studio
    6.) and its packages even more to use and programming interface is lazy and weird, but AssetStore seems even more when adding or experimenting with new projects I have to do some magic or even disable some installed packages when Unity –newProject abcd –template somePath.json(feature A,B,C, some Assets) seems broken by nature of current Unity…
    7.) autoupdating current LTS
    8.) why empty project have hundreds of MB or even GB?

Feedback usabilla icon