One other thing that should be mentioned is the debugging. Debugging files in vscode come differently now and I am talking about the launch.json and tasks.json it's a lot more work now to get them running.
No it is not. Once you setup your project properly, it works very well. VSCode is not focused on C# like VS but an universal tool, so you have to learn a bit. Fortunately, the "dotnet" command does the job for us. e.g. Launch in launch.json: { "name": "Desktop", "type": "dotnet", "request": "launch", "projectPath": "${workspaceFolder}\\.Desktop.csproj", "launchConfigurationId": "TargetFramework=;Desktop" }, Which will also connect to the debugger. Admittedly, the Project templates are a bit poor, but you can create your own templates.
If it mapped my vs shortcuts to vscode i would switch
sir how could you get that flame on your cursor? kinda cool seeing it. thanks
not to play another one of my videos... but th-cam.com/video/QO11nDyPzPU/w-d-xo.html 😊
One other thing that should be mentioned is the debugging. Debugging files in vscode come differently now and I am talking about the launch.json and tasks.json it's a lot more work now to get them running.
No it is not. Once you setup your project properly, it works very well. VSCode is not focused on C# like VS but an universal tool, so you have to learn a bit. Fortunately, the "dotnet" command does the job for us. e.g. Launch in launch.json:
{
"name": "Desktop",
"type": "dotnet",
"request": "launch",
"projectPath": "${workspaceFolder}\\.Desktop.csproj",
"launchConfigurationId": "TargetFramework=;Desktop"
},
Which will also connect to the debugger. Admittedly, the Project templates are a bit poor, but you can create your own templates.
Ah thanks for doing that, think I will stick with Visual Studio.
VS Code Pets is the VS killer
Why in the world would you ditch visual studio for VSCode to do C# development?
You are losing tons of functionality, hard pass.