4 ms·

> C# development is ideal in Visual Studio, I could look at Vs code more, especially its debugging, but I don’t think it comes close to VS. Some people like vi

> C# development is ideal in Visual Studio, I could look at Vs code more, especially its debugging, but I don’t think it comes close to VS. Some people like visual studio more but vs code works great for c# on linux. You only really need visual studio if you want the gui builder or you're doing windows c++ stuff. > I think you have to use Mono Runtime w/o Windows which has poor performance. This is just completely wrong (like 10 years out of date?). The dotnet runtime is the same on both linux and windows now as of .net core (now just ".net" as of .net 6+)

pipeline_peak 4y ago
> You only really need visual studio if you want the gui builder or you're doing windows c++ stuff VS code isn't an IDE, afaik there's no official support for .csproj, .sln, and any of the essential build automation technologies in the .NET ecosystem. There's no practical way to add NuGet packages in VS code, just 3rd party plugin city.
- resoluteteeth 4y ago
  > VS code isn't an IDE, afaik there's no official support for .csproj, .sln, and any of the essential build automation technologies in the .NET ecosystem. There's no practical way to add NuGet packages in VS code, just 3rd party plugin city. There is "official support" in that vs code will parse these files and understand nuget packages you have added, and the norm when using .net code on linux is to use the dotnet command or edit the project file directly. I guess you want more of a gui interface for these things built into the ide, in which case yes, you should probably stick to visual studio on windows, but I've used .net on linux with vs code a lot and none of these things have ever struck me as the least bit inconvenient so I guess it just depends on what you want? To put it another way, using vscode with the dotnet command on linux is a lot like using other modern languages like rust, and I don't think anyone would say that it's impossible to use vscode with rust on linux because there's no gui for adding packages.

pipeline_peak 4y ago

> You only really need visual studio if you want the gui builder or you're doing windows c++ stuff VS code isn't an IDE, afaik there's no official support for .csproj, .sln, and any of the essential build automation technologies in the .NET ecosystem. There's no practical way to add NuGet packages in VS code, just 3rd party plugin city.

resoluteteeth 4y ago
> VS code isn't an IDE, afaik there's no official support for .csproj, .sln, and any of the essential build automation technologies in the .NET ecosystem. There's no practical way to add NuGet packages in VS code, just 3rd party plugin city. There is "official support" in that vs code will parse these files and understand nuget packages you have added, and the norm when using .net code on linux is to use the dotnet command or edit the project file directly. I guess you want more of a gui interface for these things built into the ide, in which case yes, you should probably stick to visual studio on windows, but I've used .net on linux with vs code a lot and none of these things have ever struck me as the least bit inconvenient so I guess it just depends on what you want? To put it another way, using vscode with the dotnet command on linux is a lot like using other modern languages like rust, and I don't think anyone would say that it's impossible to use vscode with rust on linux because there's no gui for adding packages.