

Also, you have the choice to download the Insider edition which gives you early access to beta features. It’s cross platform, so if you’re running Mac, Windows, or Linux, you’re in luck. Start by downloading Visual Studio Code for whatever operating system you’re using. But we digress.ĭespite Microsoft’s strange naming choice, Visual Studio Code has become the most popular source editor according to a recent Stack Overflow survey. Maybe the combination of “Visual Studio” and “Code” makes it unique enough. Also, the word “Code” is so vague as to be nearly useless when used in a Google search. Since the original “Visual Studio” still exists and is completely different from Visual Studio Code, it’s easy to get the two confused in a conversation. Visual Studio Code is another one of those Microsoft products that suffers from weird-naming-convention-syndrome. The rest of this guide assumes that you’re on Windows, but the process is identical regardless of your operating system since Visual Studio Code is cross platform. You might need to augment this with sudo if your setup requires root to install software. If you’re on Linux, use your distribution’s package management commands as seen on the Linux download link.įor example, with Ubuntu, you’d use: apt install git.This link seems to redirect to Sourceforge. If you’re on Mac, use the Mac download link.If you’re on Windows, use the Windows download link.To get started, go to /downloads to find the best download for your setup. Mac and Linux have native command line support. When using Windows, you’ll most likely be using the tools included in the Git for Windows initiative (Git BASH, Git GUI, and Git Shell Integration). Git works natively on Windows, Mac, and Linux. If you’d rather use the full Visual Studio experience, we also have a huge guide to using Visual Studio 2019 with Git. We suggest you start with our extensive guide to Git and follow that up with this guide so that you know how things are working under the hood.

The downside to this is that you lose the flexibility and customization of the command line. Many developers prefer having the ability to manage repositories inline with the development environment to reduce having to context switch between applications. If you’re looking for a better experience to manage your Git repositories, this guide introduces you to using Git with Visual Studio Code.

Git’s command line has, for lack of a better way of describing it, evolved into somewhat of a conflicting journey. In learning how to use source control, you will inevitably begin using Git. Not only does source control protect you and your team from mistakes, but it also forces you into a habit of standard project organization practices. In previous articles, we’ve tried to make it clear that source control is non-negotiable to becoming a software engineer even if you work alone as an independent developer or contractor.
