All Articles in series:
Visual Studio Code Why?
Installing Visual Studio Code on OSX – From Scratch
Installing Visual Studio Code
This guide will assume a complete clean install of OSX. That means that I will cover every single pre-requisite that is required. I will also assume the reader has not much experience with OSX – if you are coming from a Windows .NET development background installation of many of the pre-requisites are not as straight forward as you’ll be used too!
Installing Code
First of all – the easy bit. Installation of the main Visual Studio Code program.
Go to https://code.visualstudio.com the website will detect you are running OSX, Windows or Linux and present you with the relevant link. Simply click the link to download the program.
This will download Visual Studio Code.app.
This is a self contained program and doesn’t require any installation. But lets move it from the default download location – which should be downloads – to the apps folder. Simple drag from the download folder onto the app folder in your Dock (if you’ve created a shortcut for it) or to the Applications folder in finder.
Now run the program by going into Applications (from finder or the Dock) and clicking it. The first time you run it you’ll be prompted to open the file as it was downloaded from the internet. Just click Open.
If you want it to be always in the Dock, right click the Icon choose options and ‘Keep In Dock’.
Another useful option for launching VS Code is to enable launch from a Terminal window. On OSX a lot can and will be performed through terminal so it’s hand to be able to simply type ‘code .’ and have it launch.
To set this launch Terminal by going to the Applications folder, then the Utilities folder and clicking ‘Terminal’. Again once running it will be handy to create a shortcut to it by right clicking it and choose Options->Keep In Dock.
What we need to do is edit a file called –bash_profile – this is like a startup file that you can use to set environment variables and things. It is also hidden. So to edit it in the Terminal window type nano ~/.bash_profile
You will be presented with a blank screen (unless you’ve installed some software that has already put some info in this.
Enter the following
code () { if [[ $# = 0 ]] then open -a "Visual Studio Code" else [[ $1 = /* ]] && F="$1" || F="$PWD/${1#./}" open -a "Visual Studio Code" --args "$F" fi }
Now press CTRL+O and accept the default filename to save the changes. Now press CRTL+X to exit nano.
Normally this script will execute on startup, but to run it now type
source ~/.bash_profile
so now if you type (with the period)
code .
VS Code will launch.
Node.js & NPM
Node.js is a JavaScript runtime execution engine. Using it you can create JavaScript applications. It is also used when building applications in VSCode to automate tasks.
Node also includes a utility called NPM – Node Package Manager. NPM is like NuGet – we can use it to install software and update software.
We will be using NPM a lot, so the next thing we need to do is install Node.
In a browser navigate to
http://nodejs.org
On the main page you will be presented with the current release of Node.js for your OS. Click the link to download the installer which be called something like node-v0.12.7.pkg (the actual name will vary depending on what the current version is). Simply run the installer by double clicking it.
In the dialog that appears click continue, then accept the license agreement, then click the install button.
Once installed you’ll be presented with a box telling you to make sure /usr/local/bin is in your path – this is so it can be executed from anywhere.
On a default OSX installation this is already set. You can confirm this by typing echo $PATH in the terminal window.
To confirm everything is working as we need now type the following
node
this will ‘launch’ nodejs and you’ll see a ‘>’. Now type
console.log(‘node is working’)
If it’s working ‘node is working’ should be output to the window. You’ll also see ‘undefined’ appear – don’t worry about that.
To quit out of node press CTRL+C twice.
Mono
The next piece of software we need is Mono. Mono is an open source implementation of .NET. Basically this means it allows you to run .NET applications on Linux and OSX based systems!
To install Mono in a browser navigate to
http://mono-project.com
Again the front page will have a link to download Mono. Click the link then double click the .pkg file that is downloaded to start the installer.
Click continue, accept the License agreement and click install.
.NET Execution Environment (ASP.NET 5)
Now we have Mono, we can install the ASP.NET 5 runtime itself. This has to be done via a terminal Window and in stages. So launch terminal (if it’s not already running).
First install the .NET Version Manager (dnvm). To do this in terminal type the following
curl -sSL https://raw.githubusercontent.com/aspnet/Home/dev/dnvminstall.sh | DNX_BRANCH=dev sh && source ~/.dnx/dnvm/dnvm.sh
This will download dnvm and automatically update your .bash_profile with the required environment settings.
Now we can use the dnvm to install or upgrade .NET Core Clr– known as the .NET Execution Environment (DNX) – by typing the following
dnvm upgrade -r coreclr
Finally, we must install DNX for Mono by typing
dnvm upgrade -r mono
The final step is we need to update our .bash_profile again. We need to ensure dnvm and dnu commands in our path, and also enable a setting to fix a IOException that we get with Mono and .NET
So again in terminal edit our profile like we did before with
Nano ~/.bash_profile
Make sure you have a reference to the dnvm.sh – it will either simply have source dnvm.sh, or a longer more verbose version.
After that line then add
Export MONO_MANAGED_WATCHER=disabled
Save the file by pressing CTRL+O
Then quit out with CTRL+X
Bower
The final software we need to install is called Bower. Bower is another package manager – like NuGet – but specifically for Web Projects.
We install Bower using NPM (The Node Package Manager). From a terminal window type the following
sudo npm install – g bowersudo tells OSX to install the package with Administrator privileges. Because of this it will prompt you for your password.
And that's it! In the next article I'll introduce you to Visual Studio Code and the .NET 5 runtime - which has a few differences to what you may be used to if you're a traditional .NET developer.
Pingback: Visual Studio Code – Why? | Brett Hargreaves