3 ms·

I remember .NET fails when there were dramas about not open sourced debugger, planning to remove hot reload (make it only available in Visual Studio because of

I remember .NET fails when there were dramas about not open sourced debugger, planning to remove hot reload (make it only available in Visual Studio because of licensing) or poor support in Visual Studio Code compared to other languages. AFAIK many people were angry that VS Code is not first class editor for C#/.NET. I am not sure how it is these days.

ozim 18d ago
Debugger was there, hot reloading was the issue. Still I take debugger in Visual studio or Rider any day instead of VSCode debugger.
- wiseowise 18d ago
  > Debugger was there, hot reloading was the issue. Was it? There was only Samsung debugger.
- mpawelski 18d ago
  it wasn't. Jetbrains can't legally use .NET's debugger, only Visual Studio and Vs Code can.
mpawelski 18d ago
The situation about debugger didn't change really. https://github.com/dotnet/core/issues/505 https://github.com/dotnet/core/issues/505 At least they didn't close the issue... https://isdotnetopen.com/ https://isdotnetopen.com/ has a good list of "dramas" questioning if .NET is truly open. At least there are not many new dramas from Microsoft... For me it's not that big of a deal that some parts are not open. At least we have good competition (Microsoft (Visual Studio, VsCode c# Dev Kit) vs Jetbrais (Rider, VsCode + recent "Resharper for VsCode" extension.) that prevents one party to mess up something big.
drewnoakes 16d ago
C# Dev Kit is also receiving huge performance improvements with .NET 11. It's available now on the pre-release version of the extension, if you want to check it out. Some details in the .NET Unboxed video here https://m.youtube.com/watch?v=5fvi7m1QxIY https://m.youtube.com/watch?v=5fvi7m1QxIY