VSCode and Unity Take Another Bold Step Forward
VSCode and Unity Take Another Bold Step Forward
Most devs however were happy to live with the constraints in the VS Code editor...that is, until NOW.
Join the DZone community and get the full member experience.Join For Free
xMatters delivers integration-driven collaboration that relays data between systems, while engaging the right people to proactively resolve issues. Read the Monitoring in a Connected Enterprise whitepaper and learn about 3 tools for resolving incidents quickly.
Today (September 10th) marks another notch in the VS Code journey to become THE lightweight multi-platform editor, the one editor to rule them all.
If you’ve been following previous articles of mine and others, there has been a big push to use VS Code’s C# features with Unity and to integrate them together seamlessly (well almost)
This wasn’t without pain, however:
- When you opened VS Code for the first time, you had to go through a process to open your project folder to get Intellisense working
- If you accidentally closed VS Code, you had to repeat the above again
- If you were working on multiple project, well it was a pain.
- Unity does not have a concept of a folder when launching an external application, so couldn’t help.
Most devs however were happy to live with these constraints as the flexibility, power and speed they got from using the editor was worth it...that is, until NOW.
Enter VS Code Version 0.8.0
The VS Code team hasn’t been sitting on their laurels, they have listened, they have watched and through it all (with the help of the community) they have acted.
As of 0.8.0, the Unity integration has gotten even tighter and most of the old hindrances have been cast aside, giving developers a much more fluid working environment (and if you are on a MAC, it’s even better #Grumble).
If you are on Windows, you’ll notice the installer also got an upgrade, so they can deliver more features directly to your machine. If you don’t like automatic updating, you can also turn that off if you wish.
Starting with the documentation, Unity has been promoted as one of the main integration’s for VS code, now with its own documentation page, which you can find here.
There’s lots of info in here, some of which I’ll highlight next.
An Integration Asset
Thanks to a community member who jumped straight on the insider track for VS Code, a Plugin has been built for Unity to streamline the integration.
To use this plugin, you need a minimum of Unity V5.0+ and VSCode 0.8.0 (for best results I found uninstalling the old version of VSCode first and then installing the latest best)
This can be found at: https://github.com/dotBunny/VSCode.
This plugin works on both MacOS and Windows and gives you the following capabilities:
- An option to enable VS Code integration (Editor –> Assets –> Enable Integration), this updates your solution files and (more importantly) keeps them in sync. This also sets the preferred external tool editor in the Unity preferences. *Note, the old “Sync MonoDevelop” option is now gone in the Unity editor from V5.2
- It writes out the necessary (and sometimes hard to find) VS Code configuration files, including the ability to hide “non-code” files in the editor (hides things like .sln, .csproj and the ever present unity .meta files) There are a couple of other settings in there to help speed up the integration.
- Automatically launches VS Code direct to your project folder, EVERY-TIME. no longer do you have to worry about keeping that window open, or switching around if you work on multiple projects
One thing to be aware of, once you enable the VSCode integration, changing your preferred code editor in the External Tools preferences will have no effect as the plugin takes over opening code files. If you want to use another editor, you’ll have to disable the integration first using the setting shown above!
These are just the main highlights as there are more features in there as well.
Currently you need to download the plugin files from GitHub but a package is going on the Unity asset store, which when it’s available, I’ll also post the link here.
Lucky Mac owners (thanks to the power of Mono) will also get debugging support in VSCode for Unity using the above plugin, which sets things all nice and neat for you.
Sadly this is Mac only (you lucky Mac people!), although there are rumours of Windows and even Linux support on the way (hopefully in the not too distant future).
The back-end of VS Code got an overhaul, predominately the version of OmniSharp used by VS code got updated. This means even more code editing features are now available and it got a slight performance boost (what more speed?)
This updates and upgrades VS Code’s features in:
- Syntax Highlighting
- Bracket matching
- Code Lens
- Go-to Definition
- Code Actions/Lightbulbs
- Go to symbol
Even more C# goodness being brought in to the editor (I’m guessing those pesky Web developers get an update as well in there somewhere)
Full Markdown Support and Markdown Preview Engine
I’m seriously considering running an offshoot blog with this feature, it’ll certainly help with my Source control markdown enabled readme files for the sites (GitHub and Bitbucket use this extensively)
By opening up any file with markdown code in it, you can simply hit Ctrl + Shift + V, and your view will be transformed in to a properly markdown converted page.
You can read more about this feature here.
You seriously don’t realise how powerful this feature is until you use it, no more pesky multiple commits to get a source control readme page updated (never mind that preview stuff, it always breaks on the website)
Into the Mix
There’s a lot to take in here, but the steps to get up and running with Unity have become far simpler.
I’d highly recommend reading the rest of the release notes for the latest release of VSCode, there are some nice surprises in there.
What’s in store in the future? Without a roadmap it’s hard to be sure, but you can expect that the VSCode team are working hard to deliver the best of the best of the best (heck, get Will smith in here to do this bit) in lightweight code editing tools.
So if you want to debug on Windows, you’ll still need full Visual Studio for the moment, but since Unity have also tightly integrated the new Visual Studio Tools for Unity and even added Visual Studio Community edition in to the Windows installer, you should be all set.
If you just want to code, then VSCode is the tool to use, when you’re ready to deploy then switch on over to full Visual Studio with your built projects (or if you need to debug for the time being, unless you are a MAC user ), either way, the future is looking pretty bright!.
Opinions expressed by DZone contributors are their own.