←back to thread

.NET 10

(devblogs.microsoft.com)
489 points runesoerensen | 1 comments | 11 Nov 25 15:44 UTC | HN request time: 0s | source
Show context
ethin ◴[12 Nov 25 12:03 UTC] No.45899130[source]▶
How is .NET debugging on the command line? I don't use IDEs that often and last time I tried making something serious with .NET I couldn't find any kind of reliable debugger that I could just spin up and get to grips with. And I wasn't exactly very keen on switching from VS build tools to full VS just to debug .NET apps.
replies(2): >>45899180 #>>45903455 #
formerly_proven ◴[12 Nov 25 12:09 UTC] No.45899180[source]▶
Isn't the official .NET debugger only allowed to be used from Visual Studio and VSC? I recall Jetbrains had to remove debugging support from their IDE for a while due to that license. Also the whole kerfuffle around hot reloading first being added to .NET (Core) and then the code being deleted because it was supposed to be a VS-only feature.

These things to me seem like one faction in MSFT wants .NET to be an open platform and another faction wants it to be a sales funnel for Visual Studio.

replies(1): >>45900342 #
jve ◴[12 Nov 25 14:06 UTC] No.45900342[source]▶
There is WinDbg which can debug CLR code, but that is Windows only.
replies(2): >>45900719 #>>45901504 #
1. trelane ◴[12 Nov 25 14:35 UTC] No.45900719[source]▶
> that is Windows only.

There are so many things that are like this in the .Net ecosystem.

Yeah, it runs on Linux. Kind of. Mostly.

As long as Microsoft is at the helm, I don't expect that to change.