Runtime: Edit and Continue support in Linux

[the-black-wolf]

What is the current state of this feature? I always sort of assumed that Roslyn was on par between platforms seeing as core was designed from ground up to be multi-platform, but I just found out that EnC apparently does not work on Linux and that Rider is passing the blame to lack of underlying support.
Its not really a show stopper, but where exactly are we with this? Is there some Linux architecture limitation that prohibits EnC?

[RussKeldorph]

@dotnet/dotnet-diag

[noahfalk]

Its primarily an issue of work and priorities rather than any architectural limitation as far as I know, and most of the work is probably in the testing. All our existing EnC tests use an old version of ildasm written in C++ against the win32 API and the classic Windows-only PDB format/APIs so we can't easily run them on Linux. Some options moving forward are that we rewrite the tests entirely or rewrite all the parts that were coupled to windows, its just work that needs to happen at some point.
HTH,
-Noah

[wocar]

Is this going to happen anytime soon? EnC is a dealbreaker. Thanks!

[nkev]

+1 From a productivity perspective, this is a really high priority for developers.

[coldwarrl]

Frankly, I do not understand why this issue does not get a higher priority.
The story of .NET core is cross-platform - but that implies you have the same productivity also cross-platform.

[wocar]

is this ever gonna happen? thanks

[wocar]

/bump

[nkev]

I thought I'd share my experience with my fellow C# developers. I've been a VB/C# dev for 24 years and never even considered another platform for a long time. Like many of you, I got sick of waiting for random spinning wheels and crashes in Visual Studio so I've given up on this "Edit and Continue in Mono" issue and have by-passed .NET altogether. I first used NodeJS with VS Code in two web projects and I could see what all the hype was about. Node has come a long way and it is so lightweight and in my experience just as fast as .NET Core for web apps (per CPU core). However, I didn't like the bloat in the NPM package manager and missed the strongly typed nature of C# and I don't like TypeScript - it's like a band aid for JS devs! So then I tried Go since it is now over 10 years old and I learned it surprisingly quickly because it's very simple. It compiles super quick directly to a native executable in any platform, so no waiting for VS to compile during dev time or a website to "warm up" (i.e. complile CLR pages again) or even installing any framework on your servers! You just upload the executable and it runs lightning fast immediately. No warm ups. It is super stable and also has a breakpoint debugger in VS-Code for Windows/Mac/Linux. There is even a Razor templating engine for it. Everybody is different of course and you may not like Go, but there are plenty of alternatives out there so I would say don't get stuck in the MS world like I did, try NodeJS, Python, Rust, Go... these languages are in high demand too. For me Go is such a breath of fresh air, that I thought I would share this with you.

[mikem8361]

/cc: @tommcdon

[wocar]

bump :(