Intro to VSCode for C# Developers - From Installation to Debugging

Visual Studio isn't the only C# editor that Microsoft makes. Visual Studio Code (VSCode) is a cross-platform development environment that can be used for development with most languages including C#. In this video, we are going to look at what VSCode is, how to install it, and how to use it to develop C# applications. The best part is that what you learn in this video will work on Windows, Mac, or Linux.

0:00 - Intro
1:18 - Getting started: Installing Visual Studio Code
5:17 - VSCode extensions
11:57 - VSCode extension setup overview: extensions used in this particular video
12:37 - Starting to use C# in VSCode
14:13 - VSCode features: Terminal, command pallet
15:49 - Windows cmd shortcut
16:38 - Note on solutions and projects
17:39 - Creating a new solution and projects with the command prompt
20:16 - Adding projects to the solution: command prompt
21:48 - Adding projects to the solution: bash prompt
23:37 - Adding a reference
24:40 - Opening project in VSCode via command prompt and VSCode debugging settings
28:13 - Working with C# project in VSCode
33:32 - Working with C# code in VSCode: running the Console app (debugging will not wok)
34:39 - Working with C# code in VSCode: launching the Console app and debugging
39:13 - Adding a NuGet references
43:25 - Concluding remarks

[snoracle]

I have only been studying C# and using Visual Studio the past 2 weeks, but one thing I'd say Visual Code does well for a beginner who is willing to take a little extra step is at least partially disambiguate the "magic" of how C# programs work compared to the perhaps overly behind the scenes nature of Visual Studio. It allows you to use a powerful text editor for programming and IntelliSense, and also makes it so you can't rely on Visual Studio but instead set it up projects yourself. I've got a lot of learning, but this helped me get going in the right direction. Thanks

[GUARDEN]

You saved my bacon. I'm in a coding bootcamp situation, and the instructor just flew threw this. I managed to keep up at the time, but I couldn't later remember the way for projects to reference one another. Thanks!

[tyrrelldavis]

17:44 solution creation on the command line part
20:50 globbing pattern and adding .sln
39:00 nuget explanation
39:50 nuget

[ryanpruneau]

I've got very little experience with programming. Ive been trying to figure out how to get started creating something basic, I have not quite seen where this all leads, but as far as operating VScode, this is by far the best tutorial I have come accross.
I can follow these steps to a T and get the same results.
Fantastic. Thanks for your help

[nishant]

27:40 Time Saver: if you got Stuck while Debugging. Thanks a lot Tim you have covered everything.

[runtomrun]

This is a fantastic intro to vscode in general, I learned so much from this I couldn't find anywhere else. Thank you

[CanadaRulezEver]

this is definitely a missing intro for Visual Studio developers who may need to migrate to VSCode and understand how to do basic things within a solution, thank you!

[stargazer]

DUDE! That cmd trick is amazing. Instant sub. Tysm.

[oguzonay]

I am trying to change the path of my career. I am working on CFD for ten years and solving fluid dynamics equation systems using FORTRAN in Linux systems (yeah I know It sounds too old school). These C# videos are really clear and believe me that they make me feel like a passionate young engineer. Really really thank you.

[TheNoar]

I don't know why I was sure that sln was not possible to use with vs code. Thank you for showing me that vs code is indeed a real usable tool

[alieltoney]

This video is brilliant. I was stuck with bunch of errors again and again, then i found this video uninstalled my apps, the follow your instructions and now everything is working well. Thanks so much

[nomadshiba]

btw you can use (shift + right-click) on in the folder window then select "Open PowerShell window here"

then you can just create your project (dotnet new console -n test)
and open it with code (code test)

idk its faster for me c:

[shawnmofid]

Thank you so much for the video. I really like VScode. I have Visual Studio Community, but I used VSCode to quickly run some Java code, and validate something. It gives you everything you need and the capability to install what you'll need later. I enjoy using it. I really like the Git support on it, and the fact that you can run it on machines you may not have admin access.

[MikeBachful]

This video explains everything so clearly, thanks so much!

[AngriestEwok]

THANK YOU! I've been tairing my hair out trying to sort all this nonsense out. New to C# DotNet, etc and the documentation really doesn't seem to cover this, which is NUTS but your video told me exactly what the problem was. I had no concept of a 'solution' and I still don't really understand what it is (meta project? workspace?) so this got me started, thanks! Subbed.

[WorldReserveCurrency]

This is the very best intro on C# projects for VSCode. Thanks!!

[hambaghini]

Nice video Tim! I've used VS Code for C# Development in the past(love the UI Design of it) but always find myself reverting to Visual Studio as my daily 'workhorse'. Both are great at the end of the day!

[notzaryab]

Thanks a lot, was very interesting explanation, I learned something new this day, and I am happy.

[spencerkaneki]

Thank you Tim so much for taking the time out of your day to teach us how to setup VSCode for C#.

[alcidesneto]

Again, thank you so much, Tim. My company decided to not buy a VS license, so instead of installing the Community version and risking my job, I prefer to use VS Code and work exclusivity with console projects. Unfortunately, that's all I can afford right now.