Installing VS Code and C# Dev Kit [Pt 2] | C# and .NET Development in VS Code for Beginners

[@MissileNearby]

thank you very much.. I'm on campus studying this.. my friends all use vs code studio to study.. only I chose vs code because I feel there is something cool here.. and I'm struggling to know the difference between vs code studio and how to use it .. finally found a playlist with this really great explanation

[@gouravpokharkar6351]

7:39 Seems like ".NET Runtime Install Tool " is renamed to ".NET Install Tool " in newer versions of C# Dev Kit

[@antonio_carvalho]

Great video with a perfect pace, thank you!

[@zacksc2574]

ive been struggling with learning c# and dotnet for a bit. its nice to know that what i was doing was correct! I learned JS first and use a mac and when i found out its better to use Visual studio for c# i was dishearted and I just recently changed from windows to mac (9 months ago lol) but i was using Visual studio on my gaming PC . So now i know VScode and visual studio. still no dev job though :( but i love coding

[@loti_iturbe]

Yeah, they are two different things. Me as a beginner I am thankful to have known visual studio first.

[@HoltBuzzing]

The C# extensions are stuck in the 'Installing' step. I have been waiting 20 minutes for them to actually get installed. I have restarted VSCode and tried from Admin mode and experienced the same results. I can install other extensions without issue.

[@g0keyn]

How can I change .net version before create my project?

[@davidconroy3891]

Nicely presented. Well done.

[@jesperkped]

I have a really annoying issue when using C# Dev Kit on vscode - it keep complaining about "The type or namespace name '***something that is known***" does not exist... Until I open the file that the type is in. The place I experience it is in for instance components for my blazor application. My projects compiles and runs without any of these issues, but for vscode to know the types I have to manually open all the files and just close them again to get vscode to remove the problems from the problems list. It makes the "Problems" list in vscode challenging to use, but also typing completion does not work until the file have been open.

[@Tarkesh01]

The dev kit is not getting installed for me

[@ekeneugwuanyi9885]

Check your network connectivity if its stable and retry again. If the above didn't work and your network connection is stable, reload vs code and try again.

[@meotisr]

No VSC for Win7 32bit 😭

[@gregory-white]

Installing vscode and dev kit is where the problems start. Testing not working. Bad documentation. Test explorer not showing. Its offering to install more extensions?? What a mess.

[@lyrichardson01]

Hi @gregory-white, sorry you’re experiencing those issues. I recently replied to another similar comment you posted in another video in this series but can you please file another issue(s) with more detail for the testing scenarios so the team can help troubleshoot? Also, can you please share more about how the documentation can be improved so we can update it? Thanks!

[@gregory-white]

Thanks for the reply. Yes, I have filed a few posts regarding this with full details. I've heard nothing back. As of today, it's still not working. I raised the issue with the dev kit team, the vscode team and the dotnet test team. I pasted the error msg that references a missing testhost-8.0.runtime.json. I verified it is missing. The document assumes when certain actions are taken, certain results will happen. The reality is different. There are potential points of failure that is not referenced by the docs.