Tbh at my job I had a problem opening 2 instances of visual studio for our different repositories for some references as it choked my system's memory. I installed vscode thinking as it is light weight and can be used for some small tweaks but had a ton of issues in doing so. Now it would be a very nice addition to my day to day work. I'll be looking forward to the updated versions as well. Kindly have a video of every major update. You are like a news channel of C# to me 😅
im a new ish developer and have only used vscode. I really wanted to learn c# but im intimidated by vs studio. Now that I saw this i feel a little bit less overwhelmed thanks corey. ill be checking out your courses
Hi! great video although i noticed when I tried following it that at 11:34 you go to a .vscode folder which doesnt seem to be there for me. I tried reinstalling vscode and the extesions and making new .net projects with no success.
I have the exact same problem. i found a way to create a .vscode folder but it did not come with a settings.json. And making my own resulted in it saying that it is a "Unknown Configuration Setting"
After Looking around for a little while i found a video which helped me find it. What you need to do is to press "CTRL + ," Then there are 3 Tabs: User, Workspace and your "folder name" Go into the one that is your folder, Then type in "code actions on save" - under that it will be a blue text that says "edit in settings.json". Click that and a settings.json and a .vscode will be created.
Just because of your video I realized how limited C# development with VSCode was so far. I must have thought all the time that I simply don't see all the relevant features of the C# extension and have been too lazy to check further because it always took me only one click to open Visual Studio instead. :-)
I don't yet on the free side. Thanks for the suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/
Hi Tim Corey thank you for sharing. I have a problem. When I run my project Debug>Start New Instance way, it runs with Hosting environment: Production configuration. I want to run it with Development Mode. How can I do it? ASPNETCORE_ENVIRONMENT variable in the launchSettings.json assigned as Development.
We’ve seen discontinuation of VS for Mac. Is this something to actually compensate for that? Can we make an assumption that this is the first step towards the same goal for Windows?
Yes and no. The C# Dev Kit for VS Code will make working with C# in VS Code much easier. There is also a MAUI plug-in if you are also doing MAUI work. However, it will always be a text editor experience rather than an IDE (like VS for Mac was). The difference is in how many features they offer in VS Code and how tightly integrated it is into a nice flow. Basically, they are not trying to replace the full Visual Studio experience with VS Code (although that would be nice). If you want a full IDE, you would need to pay for JetBrains Rider. If you don't mind the limitations of a text editor, VS Code will be an excellent solution for you.
I am not sure what you are asking. Yes, you can use VS Code to build a large software application in C#. You can use the C# Dev Kit to build that application on Linux or Windows in the same way. Does that answer your question?
The pre-release version has a task for running .NET watch on your project (which is hot reload). However, I was not able to get it to successfully reload on a simple change to a Blazor page. I believe it still needs a bit of work.
You don't need to delete profiles. Instead of debugging by right clicking the project, you can go to the run and debug tab on the left hand side. Once there you will be able to select any profile in your launch settings to debug with.
The solution doesn't launch that way, though. That's for the VSCode Run and Debug dialog and it isn't set up by the C# Dev Kit. You need to set up a launch.json file and configure it in order to have profiles for the drop-down menu. Eventually, the C# Dev Kit will probably add those, but for now, they don't come out of the box.
@@IAmTimCorey ok I see what you mean. I just want them to add nuget package manager now and a way to view source code for libraries. Then I'll move over.
Coming from Node JS backend dev, I always find Visual Studio overwhelming with too much UI rather than just using terminal for everything in Node JS. Since now I know how to use VS Code for C# dev, I find it much easier to transition into.
That's a good observation. VS has a TON of options, which is great when you need them, but is really overwhelming when you start out. In fact, probably most C# developers still don't use C# to its fullest. I'm glad VSCode is helping you transition more easily.
this is great for me cause i use linux and i always wanted to learn c# now i can i will be trying it out today next step is to find a great course to help me learn it
Vscode is faster than visual studio. So can we drop using visual studio and keep using only vscode to develop in c#? I mean is vscode full of all the features we're goign to need to develop all kind of c# applications ?
You can definitely use VS Code to develop C# applications, but that doesn't mean it negates the value of Visual Studio. First, VS can do a LOT VS Code cannot, including .NET Framework, WinForms, WPF, UWP, etc. Second, VS has a LOT more features around making and debugging your code that VS Code does not have yet.
There was, although that was just limited to the solution explorer window (although it did more than the C# dev kit does currently with that window). However, this is more than that. It is testing, Intellicode, running/debugging the project and more. Also, this is the official package from Microsoft, which matters to some people.
I felt like the pre-release C# extension dropped a bunch of stuff that wasn't added in the dev kit so I ended up going back after a few days. I'll probably try it again when it's a bit more mature though
You can't. You have to use a terminal instead. C# support in VS Code is absolutely awful. A great example of Microsoft heading back to the "old days" of forcing people to use Windows
No, that is a Windows-only feature and only part of Visual Studio. VSCode is cross-platform, so it won't get the visual designers for WinForms or WPF. Both of them rely on Windows-only dlls to render.
tried it after watching your video, it works but it also took up 10 GB of my ram in .net host processes for a project of medium size with 54 tiny modules. had to disable it.
Hey! New to your channel, I been bouncing through your videos and watching them on a binge! Love your content! Do you think you'll ever do a tutorial or anything on something like PetaPoco or Npoco? Thanks for the great videos!
@@IAmTimCorey To create a TH-cam playList like 10-Minutes Training Videos playlist or Dev Questions Answered playlist, but with videos of practical C# series.
OK, but what would be in it? I have hundreds of C# videos on this channel. It would end up being half of all the videos on the channel if it were about C#.
@@IAmTimCoreyVideos like this: "c# dev kit for VSCode" or "Generating Fake Data with Bogus" for grouping them in a playlist like Dev Questions Answered
It is cross-platform, so it will work on Mac and Linux the same way. Also, it is quick for things you need to do. Also, it is a much smaller download and can run better with low system requirements.
It's a little rough going from operating for free through VSC to essentially a VS Pro license when using this in an enterprise. It's not a total deal breaker, but for that price i might rather use Rider. maybe when it's developed to include more features i'd consider adding dev kit, but i'm glad there's new rising competition for Rider.
It doesn't require a VS Pro license. I'm not sure who is saying that, but it isn't true. It is under the same license as Visual Studio 2022 Community Edition. It is free to use for individuals and organizations that make less than $1,000,000 annually. Also, you can use C# on VSCode for free as always. That didn't change. It is only the tooling that they brought from Visual Studio that they kept under the same license as Visual Studio.
Excuseme me master if the question i want to ask you is a bit out of content of the video. I am interested in acquiring one of your courses. I have been reviewing several videos on the channel and according to what i have understood for my case, which is web application development, in which i want to emphasize i must start with the fundamentals of the language in depth (C# Mastercourse) then learn HTML, CSS and vainilla Javascript in depth and then continue in the course(Web development mastercourse)
Basically, yes. The C# Mastercourse is the right place to start. Since you want to learn web development, the Web Development Mastercourse is the next right step after that. You don't need to do any pre-learning for either of those courses, though. They both start from the very beginning of their topics.
No, it is licensed for VSCode. They are bringing in the tools from Visual Studio, so they still have the Visual Studio licensing requirements attached.
@@IAmTimCorey sorry, I'm switching from python to c#, I do all the stuff in python within terminal, can I do everything that this dev kit offer within terminal too?
You don't need the C# dev kit for that. The dotnet command line will do everything you need. Here is a video explaining how to use it: th-cam.com/video/RQLzp2Z8-BE/w-d-xo.html
Great video as usual. but I don't know why one would use VS code instead of VS when with this extension it's basically trying to reinvent the wheel. No need to mention that when it's come to license it's also the same thing.
It isn't trying to reinvent the wheel. It is providing options. Options that are badly needed and greatly desired. For instance, this works the same on Windows, Mac, and Linux. That's something that VS doesn't do. Also, this allows people to interact with C# projects more easily in their preferred environment. Like I mentioned in the video, my web developer is just focused on the HTML and CSS of my C# application. Visual Studio did not work well for him, but VSCode works great. There are lots of reasons why this is valuable.
A good use case for me: being able to use VS Code to write C# programs is another step toward making C# a viable scripting language to write simple utility console apps. VS Code provides a lighter-weight environment for writing these kinds of apps rather than having to install full-blown Visual Studio. For me, it'll be a viable alternative to Python or PowerShell.
There are lots of reasons for this to exist. For instance, this works the same on Windows, Mac, and Linux. That's something that VS doesn't do. Also, this allows people to interact with C# projects more easily in their preferred environment. Like I mentioned in the video, my web developer is just focused on the HTML and CSS of my C# application. Visual Studio did not work well for him, but VSCode works great. There are lots of reasons why this is valuable.
Not worth it yet, but I guess they just can't seem to figure out how to make VS better, and if they continue to let the VSCode C# dev experience stagnate they'll soon find themselves in a world where everyone uses (or wants to use) Rider for C#.
This has nothing to do with Visual Studio or its development. This is about providing options for those already using VSCode as their primary development system or for people who want the cross-platform development option (such as Linux users). As for Visual Studio, they absolutely have found ways to make VS better. For instance, they just built in http files for API testing, they added GitHub Copilot X for inline AI help, and LOTS more. They are releasing new, powerful features about every six weeks now. Even the "small" updates are great, such as sticky scroll, colorized braces, and spell checking.
visual studio should die, old, not open source, buggy, miserable interface, long response time, works poorly with everything except c# and c++, has paid subscriptions, the default version does not have the basic things that vscode has from the start. It is high time for Microsoft to focus on vscode, because even before the advent of the c# dev kit, vscode could compete with rider (vs was terribly behind him). So my hope is that vs is finally buried by moving to vscode and the next step for c# is to add an interface to nuget.
I’m not sure if you just haven’t used Visual Studio or if you just ignore all the good when evaluating. Every video I have created for the past couple of years has been using the free version of Visual Studio. It isn’t limited. In fact, I is the same as the Professional edition, just with a different license. It was designed for C# and C++ so I’m not sure what you are complaining about. It is continually being updated with new features (Copilot, Intellicode, GitHub integrations, and more). And if you think that it’s features are even close to VSCode, you aren’t really using any of VS’s power.
@@IAmTimCorey I would turn a blind eye to many things if it were not for this laggy interface, which is equally buggy on all devices. Last time I left vs because it didn't have gitlens in the community edition. Rider is way ahead of vs, but if you suddenly don't have the opportunity to buy it, then vscode is a great way out, only some of the tools will not be available to you through ui, for example, nuget. And I do not want to offend anyone, but I do not understand how someone can use VS. Recently, I saw VS 2019 (in 2023) at one of my colleagues, he didn’t even know that you can watch the resources of the decompiled code, until I told him, he thought that you can only watch signatures. And most of my colleagues use VS, not because they've tried rider or vscode, but because they're used to it, that's all. People become very addicted to the tools they use, and often because of this, they miss the appearance of more convenient options.
Microsoft has no strategy. They keep throwing things at the wall until something sticks. Visual Studio 20xx was once a great IDE, but no longer cares about its GUI. They no longer bother creating nicely laid out UIs and WYSIWYG designers, instead they just have script runners and configuration files. It's also becoming very slow to the point of being unusable. VSCode is built on Electron instead of a real GUI platform.
That's not a great take. They absolutely care about the VS GUI. For instance, in the past couple of months, they've added GitHub Copilot and Copilot X, spell checking, sticky scroll, colorized braces, lots of new GitHub integrations (better linking of issues to pull requests and commits, etc.), lots of new Azure automations (automatic GitHub action file creation based upon deployment, etc.), breakpoint groups, IEnumerable visualization on debug, the compact new file dialog box, quick actions and refactoring improvements, Intellicode directing Copilot, and LOTS more. That's just in the past couple of months. As for the speed of VS, they make improvements to speed in almost every release. That doesn't mean that every scenario gets faster, though. VSCode was built on a real GUI platform. In fact, building it on Electron was a brilliant idea. Not only does it work really well and load REALLY fast, but it also works on Mac and Linux in the same way that it works on Windows. That's HUGE! But it doesn't stop there. Have you seen GitHub Codespaces? You can set up a pre-built VSCode environment that loads in the browser and yet has the same power as if it were running on a desktop. Basically, you can run VSCode anywhere. Oh, and it is the most popular text editor for the web on the planet (citation: survey.stackoverflow.co/2022/#section-most-popular-technologies-integrated-development-environment ).
@@IAmTimCorey Oh really? Do you recall the big mess over managing packages in visual studio? When Microsoft started embracing open source JavaScript frameworks and tooling, they added half-baked Visual Studio facilities for managing the millions of packages for them. Nuget package manager was completely inept at handling them properly. It couldn't install them in a project according to their conventions. Microsoft's solution was Libman which was a crappy UI that barely worked. Instead of controlling the developer experience, they just leveraged NPM which ran as another process and caused your entire solution to come screeching to a halt. It was so bad, developers gave up on VS and went straight to the command-line, others started using Visual Studio Code because it was less painful as far as performance. You tell me, how is it possible for an Electron based app, an interpreted JavaScript and rendered HTML running inside a bloated browser, to outperform a dedicated, native Windows application written in C++? The answer is easy. Microsoft blew it! Fortunately, there's Visual Studio for Mac 2022 which is surprisingly speedy, but it lacks a bunch of the functionality found in the Windows version. The real issue is that Microsoft doesn't have a good GUI story since Win32. They had WPF but they self-sabotaged it in order to support JS/HTML. Now they're trying to get us excited about MAUI. So far, the demos have all been the same Purple bot on the page. When I looked at the Repo I held my judgement, but lo and behold, it's just warmed over Xamarin! Surprise! It's about as exciting as a botulin laced meatloaf sandwich. Ironically, they're productivity products have fairly decent GUIs that work well across platforms.
@bob - I never said Microsoft always makes perfect decisions. Yep, they made a messy attempt at doing their own thing for web development. They have a habit of wanting to control the system (their own libman instead of npm, etc.) While that typically makes a mess, I also understand why they want to do it. Look at all of the applications that have failed/closed because they relied on Twitter or Reddit recently. Building your application to be reliant on an external system is a dangerous proposition. As for your continued attack on VSCode not being as good as a "native Windows application", that's the problem. They weren't trying to create a GUI to replace Visual Studio. They had an entirely different goal. The goal was to build the best text editor on the planet that could work on any platform. Since their goal was different than what you want, of course it isn't going to meet your expectations. Visual Studio for Mac doesn't have the functionality that VS for Windows does for a few reasons. First, it has a LOT of catching up to do. Second, .NET Framework and WinForms/WPF/UWP/etc. are all tied to Windows, so the Mac version of VS will always have less options/features compared to the Windows version. I agree that the desktop options for C# aren't great. However, your assessment of .NET MAUI is...weird. It isn't "warmed over Xamarin". It is the upgrade to Xamarin. They were very clear about that. They upgraded Xamarin to use .NET 6 so that everything worked on the same .NET compiler. From there, they started adding more features (although the big focus has been on stability and replacing existing features). We are one year into what turned out to be basically a major rewrite of a major system. That's pretty good for so little time.
@@IAmTimCorey Aside from occasional OmniSharp issues, lack of maturity in the debugging tools I have not noticed any problems with the C# experience in VSCode. Certainly nothing motivating me to want to pay a subscription for additional features.
@@IAmTimCorey I mean look at the feature list Project System / Solution Explorer - We already have a file tree Solution Node Actions: Meh Add Project: Just use the terminal Build/Run Project: We already have this Code Editing (Uses the C# extension): We already have this Refactoring: We already have refactoring tools Code Navigation (Go To Definition/References): We already have code navication tools Code Completions: We already have code completion Roslyn powered semantic awareness: Isnt omnisharp powered by Roslyn? Package Management: We already have this but again just use terminal Automatic NuGet Restore: We already have this but again just use terminal Testing: We already have this ... Discover, Run, and Debug Tests again we already have this. So what is new?
What's new is the GUI. Without using the C# Dev Kit, how do you create a new project? Command line. How do you associate a project with a solution? Command line. How do you run the unit tests? Command line. Run the project? Create a launch.json file, tweak it for your particular settings, then using the GUI. All of these became faster and easier with the Dev Kit. As for the pricing, it is free under the same licensing as Visual Studio 2022 Community Edition. It is free for individuals and companies with 5 or less developers where the company income is less than $1,000,000 annually. It is also free for all open source projects.
Tbh at my job I had a problem opening 2 instances of visual studio for our different repositories for some references as it choked my system's memory. I installed vscode thinking as it is light weight and can be used for some small tweaks but had a ton of issues in doing so. Now it would be a very nice addition to my day to day work. I'll be looking forward to the updated versions as well. Kindly have a video of every major update. You are like a news channel of C# to me 😅
I'm glad my content has been helpful.
Linux users were waiting for this :)
Yeah, it’s a nice addition for them.
And Mac!
im a new ish developer and have only used vscode. I really wanted to learn c# but im intimidated by vs studio. Now that I saw this i feel a little bit less overwhelmed thanks corey. ill be checking out your courses
Great! I’m glad you are feeling more confident.
Thank you! TimCorey for the awesome video ✨
You are welcome.
12:33 how to rid off message "Failed to read environment variable [DOTNET_ROOT]...." ?
Hi! great video although i noticed when I tried following it that at 11:34 you go to a .vscode folder which doesnt seem to be there for me. I tried reinstalling vscode and the extesions and making new .net projects with no success.
I have the exact same problem. i found a way to create a .vscode folder but it did not come with a settings.json.
And making my own resulted in it saying that it is a "Unknown Configuration Setting"
After Looking around for a little while i found a video which helped me find it. What you need to do is to press "CTRL + ," Then there are 3 Tabs: User, Workspace and your "folder name"
Go into the one that is your folder, Then type in "code actions on save" - under that it will be a blue text that says "edit in settings.json". Click that and a settings.json and a .vscode will be created.
@@zilkyy3111 Thanks for this. Saved me time.
Just because of your video I realized how limited C# development with VSCode was so far. I must have thought all the time that I simply don't see all the relevant features of the C# extension and have been too lazy to check further because it always took me only one click to open Visual Studio instead. :-)
It wasn't designed to be a C# IDE. At its heart, it is just a text editor. This definitely makes working with C# easier, though.
I do not have a vscode in my explorer so i can not access the settings file. Everything else is present. :(
C# Dev Kit requires .Net SDK. Do you have a video covering the complete installment, including C# extensions for VSCode, SDK, path settings etc?
I don't yet on the free side. Thanks for the suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/
Hi Tim Corey thank you for sharing. I have a problem. When I run my project Debug>Start New Instance way, it runs with Hosting environment: Production configuration. I want to run it with Development Mode. How can I do it? ASPNETCORE_ENVIRONMENT variable in the launchSettings.json assigned as Development.
We’ve seen discontinuation of VS for Mac. Is this something to actually compensate for that?
Can we make an assumption that this is the first step towards the same goal for Windows?
Yes and no. The C# Dev Kit for VS Code will make working with C# in VS Code much easier. There is also a MAUI plug-in if you are also doing MAUI work. However, it will always be a text editor experience rather than an IDE (like VS for Mac was). The difference is in how many features they offer in VS Code and how tightly integrated it is into a nice flow. Basically, they are not trying to replace the full Visual Studio experience with VS Code (although that would be nice). If you want a full IDE, you would need to pay for JetBrains Rider. If you don't mind the limitations of a text editor, VS Code will be an excellent solution for you.
Fair enough. Thanks! 👍
impresionant!
devcontainer VSCode for python and net?
So is this the best option we have for developing with C# on MacOS? For those of us that don't want to pay for JetBrains Rider that is?
No, you also have Visual Studio for Mac.
@@IAmTimCorey Isn't that considered to be "bad" though?
No, it has been updated a lot recently and is a good option.
we won't have that anymore in 2024 since it will be abandoned...@@IAmTimCorey
Not an option anymore. They are getting rid of it as you will see in another one of Tim’s videos.
Wow this is Awesome! This will be very helpful!
I'm glad.
Can you write a large software program with a visual code from scratch by using plug-ins in linux or in Windows?
I am not sure what you are asking. Yes, you can use VS Code to build a large software application in C#. You can use the C# Dev Kit to build that application on Linux or Windows in the same way. Does that answer your question?
Yes, thanks for answering my question
That's amazing!! Can you answer me. Vs code does not show me error when I write wrong syntax in C#. How can I fix it. Please
Do you have the C# Dev Kit installed? Are you working in a .cs file?
Thank you for sharing this. It is very helpful.
You are so welcome!
Does the dev kit support hot reload or live server on mvc pages as it's much easier to edit frontend using it.
The pre-release version has a task for running .NET watch on your project (which is hot reload). However, I was not able to get it to successfully reload on a simple change to a Blazor page. I believe it still needs a bit of work.
You don't need to delete profiles.
Instead of debugging by right clicking the project, you can go to the run and debug tab on the left hand side. Once there you will be able to select any profile in your launch settings to debug with.
The solution doesn't launch that way, though. That's for the VSCode Run and Debug dialog and it isn't set up by the C# Dev Kit. You need to set up a launch.json file and configure it in order to have profiles for the drop-down menu. Eventually, the C# Dev Kit will probably add those, but for now, they don't come out of the box.
@@IAmTimCorey ok I see what you mean.
I just want them to add nuget package manager now and a way to view source code for libraries. Then I'll move over.
Coming from Node JS backend dev, I always find Visual Studio overwhelming with too much UI rather than just using terminal for everything in Node JS. Since now I know how to use VS Code for C# dev, I find it much easier to transition into.
That's a good observation. VS has a TON of options, which is great when you need them, but is really overwhelming when you start out. In fact, probably most C# developers still don't use C# to its fullest. I'm glad VSCode is helping you transition more easily.
this is great for me cause i use linux and i always wanted to learn c# now i can i will be trying it out today next step is to find a great course to help me learn it
Awesome!
Vscode is faster than visual studio. So can we drop using visual studio and keep using only vscode to develop in c#? I mean is vscode full of all the features we're goign to need to develop all kind of c# applications ?
You can definitely use VS Code to develop C# applications, but that doesn't mean it negates the value of Visual Studio. First, VS can do a LOT VS Code cannot, including .NET Framework, WinForms, WPF, UWP, etc. Second, VS has a LOT more features around making and debugging your code that VS Code does not have yet.
@@IAmTimCorey Thanks for your feedback Mr Corey, I appreciated 😊
Does anyone know why when you install the c# extension another called NET install tool for extension authors is installed which cannot be uninstalled?
It is probably a dependency.
There is a solution explorer vs code extension that already provide same kind of functionality
There was, although that was just limited to the solution explorer window (although it did more than the C# dev kit does currently with that window). However, this is more than that. It is testing, Intellicode, running/debugging the project and more. Also, this is the official package from Microsoft, which matters to some people.
@@IAmTimCoreythank you for clarification
This is different from .NET extension pack?
Yes, it is different. The .NET Extension Pack actually seems out of date (even though it is in preview). The last update was a year ago.
I felt like the pre-release C# extension dropped a bunch of stuff that wasn't added in the dev kit so I ended up going back after a few days. I'll probably try it again when it's a bit more mature though
It definitely was an early look at the tool, but they keep making improvements (and now there is an add-on for MAUI and another for Unity).
How do I make a forms application?
You don't in VS Code. You can only do that on Visual Studio (the full Windows IDE) because only Windows has the required dlls that WinForms relies on.
@@IAmTimCorey yea was hoping there was a way but I just end up doing an rdp from my Mac to my windows. Keep up the great videos Tim!
@@MadPo- then do: dotnet build, then do dotnet run
Hello,can you please explain how nuget packages can be added in projects in vs code?
You would use the commandl ine: learn.microsoft.com/en-us/nuget/quickstart/install-and-use-a-package-using-the-dotnet-cli
You can't. You have to use a terminal instead. C# support in VS Code is absolutely awful. A great example of Microsoft heading back to the "old days" of forcing people to use Windows
Will it be possible to develop Windows Form apps with the designer tool as VS too?
No, that is a Windows-only feature and only part of Visual Studio. VSCode is cross-platform, so it won't get the visual designers for WinForms or WPF. Both of them rely on Windows-only dlls to render.
tried it after watching your video, it works but it also took up 10 GB of my ram in .net host processes for a project of medium size with 54 tiny modules. had to disable it.
That's the result of VS Code being a web application under the covers.
Is this a replacement for the existing “C#” extension by Microsoft?
No, it is in addition to it to make it more powerful.
Can you make a video about WebGPU, and does this affect Desktop/Mobile Development?
Hey! New to your channel, I been bouncing through your videos and watching them on a binge! Love your content! Do you think you'll ever do a tutorial or anything on something like PetaPoco or Npoco?
Thanks for the great videos!
Thanks for the suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/
Great videos all of them! One suggestion, could be a list of all videos from PRACTICAL C#??
I'm not sure what you mean. Can you please explain?
@@IAmTimCorey To create a TH-cam playList like 10-Minutes Training Videos playlist or Dev Questions Answered playlist, but with videos of practical C# series.
OK, but what would be in it? I have hundreds of C# videos on this channel. It would end up being half of all the videos on the channel if it were about C#.
@@IAmTimCoreyVideos like this: "c# dev kit for VSCode" or "Generating Fake Data with Bogus" for grouping them in a playlist like Dev Questions Answered
Why would I use vscode over vs?
It is cross-platform, so it will work on Mac and Linux the same way. Also, it is quick for things you need to do. Also, it is a much smaller download and can run better with low system requirements.
@@IAmTimCorey thaanks
Tnx a lot Tim!
How can I add the Test button into VSCode?
It is part of the Dev Kit.
@@IAmTimCorey Strange.
I've installed the Dev Kit but don't have any Test button in the left panel
You should get if you have test project else just navigate to View > Testing
@@sanampakuwal Tnx.👍
It's a little rough going from operating for free through VSC to essentially a VS Pro license when using this in an enterprise. It's not a total deal breaker, but for that price i might rather use Rider. maybe when it's developed to include more features i'd consider adding dev kit, but i'm glad there's new rising competition for Rider.
It doesn't require a VS Pro license. I'm not sure who is saying that, but it isn't true. It is under the same license as Visual Studio 2022 Community Edition. It is free to use for individuals and organizations that make less than $1,000,000 annually. Also, you can use C# on VSCode for free as always. That didn't change. It is only the tooling that they brought from Visual Studio that they kept under the same license as Visual Studio.
Excuseme me master if the question i want to ask you is a bit out of content of the video. I am interested in acquiring one of your courses. I have been reviewing several videos on the channel and according to what i have understood for my case, which is web application development, in which i want to emphasize i must start with the fundamentals of the language in depth (C# Mastercourse) then learn HTML, CSS and vainilla Javascript in depth and then continue in the course(Web development mastercourse)
Basically, yes. The C# Mastercourse is the right place to start. Since you want to learn web development, the Web Development Mastercourse is the next right step after that. You don't need to do any pre-learning for either of those courses, though. They both start from the very beginning of their topics.
can other ides and editors use this as well like vim or rider
No, it is licensed for VSCode. They are bringing in the tools from Visual Studio, so they still have the Visual Studio licensing requirements attached.
Does this better than using keyboard only?
Keyboard only? Not sure what you mean.
@@IAmTimCorey sorry, I'm switching from python to c#, I do all the stuff in python within terminal, can I do everything that this dev kit offer within terminal too?
You don't need the C# dev kit for that. The dotnet command line will do everything you need. Here is a video explaining how to use it: th-cam.com/video/RQLzp2Z8-BE/w-d-xo.html
@@IAmTimCorey ty
Has anyone noticed if this works on a Mac okay? I have a 2021 M1
It does work cross-platform, so it should be fine, but I haven't tested it yet.
Great video as usual. but I don't know why one would use VS code instead of VS when with this extension it's basically trying to reinvent the wheel. No need to mention that when it's come to license it's also the same thing.
It isn't trying to reinvent the wheel. It is providing options. Options that are badly needed and greatly desired. For instance, this works the same on Windows, Mac, and Linux. That's something that VS doesn't do. Also, this allows people to interact with C# projects more easily in their preferred environment. Like I mentioned in the video, my web developer is just focused on the HTML and CSS of my C# application. Visual Studio did not work well for him, but VSCode works great. There are lots of reasons why this is valuable.
I agree with Tim. I love the vscode keybinds. There are some I wish I had in visual studio so its nice to have both options to use.
A good use case for me: being able to use VS Code to write C# programs is another step toward making C# a viable scripting language to write simple utility console apps. VS Code provides a lighter-weight environment for writing these kinds of apps rather than having to install full-blown Visual Studio. For me, it'll be a viable alternative to Python or PowerShell.
Visual Studio works fine. What's the point of this?
There are lots of reasons for this to exist. For instance, this works the same on Windows, Mac, and Linux. That's something that VS doesn't do. Also, this allows people to interact with C# projects more easily in their preferred environment. Like I mentioned in the video, my web developer is just focused on the HTML and CSS of my C# application. Visual Studio did not work well for him, but VSCode works great. There are lots of reasons why this is valuable.
Not worth it yet, but I guess they just can't seem to figure out how to make VS better, and if they continue to let the VSCode C# dev experience stagnate they'll soon find themselves in a world where everyone uses (or wants to use) Rider for C#.
This has nothing to do with Visual Studio or its development. This is about providing options for those already using VSCode as their primary development system or for people who want the cross-platform development option (such as Linux users). As for Visual Studio, they absolutely have found ways to make VS better. For instance, they just built in http files for API testing, they added GitHub Copilot X for inline AI help, and LOTS more. They are releasing new, powerful features about every six weeks now. Even the "small" updates are great, such as sticky scroll, colorized braces, and spell checking.
@@IAmTimCorey Prob has something to do with the deprecation of VS for Mac.
C# Dev Kids here
👋
visual studio should die, old, not open source, buggy, miserable interface, long response time, works poorly with everything except c# and c++, has paid subscriptions, the default version does not have the basic things that vscode has from the start. It is high time for Microsoft to focus on vscode, because even before the advent of the c# dev kit, vscode could compete with rider (vs was terribly behind him). So my hope is that vs is finally buried by moving to vscode and the next step for c# is to add an interface to nuget.
I’m not sure if you just haven’t used Visual Studio or if you just ignore all the good when evaluating. Every video I have created for the past couple of years has been using the free version of Visual Studio. It isn’t limited. In fact, I is the same as the Professional edition, just with a different license.
It was designed for C# and C++ so I’m not sure what you are complaining about.
It is continually being updated with new features (Copilot, Intellicode, GitHub integrations, and more).
And if you think that it’s features are even close to VSCode, you aren’t really using any of VS’s power.
@@IAmTimCorey I would turn a blind eye to many things if it were not for this laggy interface, which is equally buggy on all devices. Last time I left vs because it didn't have gitlens in the community edition. Rider is way ahead of vs, but if you suddenly don't have the opportunity to buy it, then vscode is a great way out, only some of the tools will not be available to you through ui, for example, nuget.
And I do not want to offend anyone, but I do not understand how someone can use VS. Recently, I saw VS 2019 (in 2023) at one of my colleagues, he didn’t even know that you can watch the resources of the decompiled code, until I told him, he thought that you can only watch signatures.
And most of my colleagues use VS, not because they've tried rider or vscode, but because they're used to it, that's all. People become very addicted to the tools they use, and often because of this, they miss the appearance of more convenient options.
Microsoft has no strategy. They keep throwing things at the wall until something sticks. Visual Studio 20xx was once a great IDE, but no longer cares about its GUI. They no longer bother creating nicely laid out UIs and WYSIWYG designers, instead they just have script runners and configuration files. It's also becoming very slow to the point of being unusable. VSCode is built on Electron instead of a real GUI platform.
That's not a great take. They absolutely care about the VS GUI. For instance, in the past couple of months, they've added GitHub Copilot and Copilot X, spell checking, sticky scroll, colorized braces, lots of new GitHub integrations (better linking of issues to pull requests and commits, etc.), lots of new Azure automations (automatic GitHub action file creation based upon deployment, etc.), breakpoint groups, IEnumerable visualization on debug, the compact new file dialog box, quick actions and refactoring improvements, Intellicode directing Copilot, and LOTS more. That's just in the past couple of months. As for the speed of VS, they make improvements to speed in almost every release. That doesn't mean that every scenario gets faster, though.
VSCode was built on a real GUI platform. In fact, building it on Electron was a brilliant idea. Not only does it work really well and load REALLY fast, but it also works on Mac and Linux in the same way that it works on Windows. That's HUGE! But it doesn't stop there. Have you seen GitHub Codespaces? You can set up a pre-built VSCode environment that loads in the browser and yet has the same power as if it were running on a desktop. Basically, you can run VSCode anywhere. Oh, and it is the most popular text editor for the web on the planet (citation: survey.stackoverflow.co/2022/#section-most-popular-technologies-integrated-development-environment ).
@@IAmTimCorey Oh really? Do you recall the big mess over managing packages in visual studio? When Microsoft started embracing open source JavaScript frameworks and tooling, they added half-baked Visual Studio facilities for managing the millions of packages for them. Nuget package manager was completely inept at handling them properly. It couldn't install them in a project according to their conventions. Microsoft's solution was Libman which was a crappy UI that barely worked. Instead of controlling the developer experience, they just leveraged NPM which ran as another process and caused your entire solution to come screeching to a halt. It was so bad, developers gave up on VS and went straight to the command-line, others started using Visual Studio Code because it was less painful as far as performance. You tell me, how is it possible for an Electron based app, an interpreted JavaScript and rendered HTML running inside a bloated browser, to outperform a dedicated, native Windows application written in C++? The answer is easy. Microsoft blew it! Fortunately, there's Visual Studio for Mac 2022 which is surprisingly speedy, but it lacks a bunch of the functionality found in the Windows version.
The real issue is that Microsoft doesn't have a good GUI story since Win32. They had WPF but they self-sabotaged it in order to support JS/HTML. Now they're trying to get us excited about MAUI. So far, the demos have all been the same Purple bot on the page. When I looked at the Repo I held my judgement, but lo and behold, it's just warmed over Xamarin! Surprise! It's about as exciting as a botulin laced meatloaf sandwich. Ironically, they're productivity products have fairly decent GUIs that work well across platforms.
The strategy is web dev. Selling cloud services is a lot more lucrative than making IDEs.
@bob - I never said Microsoft always makes perfect decisions. Yep, they made a messy attempt at doing their own thing for web development. They have a habit of wanting to control the system (their own libman instead of npm, etc.) While that typically makes a mess, I also understand why they want to do it. Look at all of the applications that have failed/closed because they relied on Twitter or Reddit recently. Building your application to be reliant on an external system is a dangerous proposition.
As for your continued attack on VSCode not being as good as a "native Windows application", that's the problem. They weren't trying to create a GUI to replace Visual Studio. They had an entirely different goal. The goal was to build the best text editor on the planet that could work on any platform. Since their goal was different than what you want, of course it isn't going to meet your expectations.
Visual Studio for Mac doesn't have the functionality that VS for Windows does for a few reasons. First, it has a LOT of catching up to do. Second, .NET Framework and WinForms/WPF/UWP/etc. are all tied to Windows, so the Mac version of VS will always have less options/features compared to the Windows version.
I agree that the desktop options for C# aren't great. However, your assessment of .NET MAUI is...weird. It isn't "warmed over Xamarin". It is the upgrade to Xamarin. They were very clear about that. They upgraded Xamarin to use .NET 6 so that everything worked on the same .NET compiler. From there, they started adding more features (although the big focus has been on stability and replacing existing features). We are one year into what turned out to be basically a major rewrite of a major system. That's pretty good for so little time.
0:27 Err what? No he doesnt.
That’s the easiest solution. Yes, there are other options including VSCode, but this makes it easier.
@@IAmTimCorey Aside from occasional OmniSharp issues, lack of maturity in the debugging tools I have not noticed any problems with the C# experience in VSCode. Certainly nothing motivating me to want to pay a subscription for additional features.
@@IAmTimCorey If its free great. Better tooling is always welcome. But its hardly inhibiting currently.
@@IAmTimCorey I mean look at the feature list
Project System / Solution Explorer - We already have a file tree
Solution Node Actions: Meh
Add Project: Just use the terminal
Build/Run Project: We already have this
Code Editing (Uses the C# extension): We already have this
Refactoring: We already have refactoring tools
Code Navigation (Go To Definition/References): We already have code navication tools
Code Completions: We already have code completion
Roslyn powered semantic awareness: Isnt omnisharp powered by Roslyn?
Package Management: We already have this but again just use terminal
Automatic NuGet Restore: We already have this but again just use terminal
Testing: We already have this ...
Discover, Run, and Debug Tests again we already have this.
So what is new?
What's new is the GUI. Without using the C# Dev Kit, how do you create a new project? Command line. How do you associate a project with a solution? Command line. How do you run the unit tests? Command line. Run the project? Create a launch.json file, tweak it for your particular settings, then using the GUI. All of these became faster and easier with the Dev Kit. As for the pricing, it is free under the same licensing as Visual Studio 2022 Community Edition. It is free for individuals and companies with 5 or less developers where the company income is less than $1,000,000 annually. It is also free for all open source projects.