Edit & Continue not working

[MihaMarkic]

Hi guys,

I'm looking at asp.net beta8 and it seems that Edit & Continue doesn't work with it. I mean I can pause, change some code, run again – but changes aren’t visible in browser and breakpoints get disabled.
Is that related to asp.net beta or it has to do with Visual Studio?
I know I could use dnx-watcher but then the debugging is lost (unless reattached at start and after every change).

[BillHiebert]

This is likely a side effect of the new hosting model where the dnx process is started by IIS Express. We need to do more investigation to understand why as VS 2015 does support ENC when attaching.

[BillHiebert]

Sorry, ENC never worked for dnx projects because of the dynamic compilation (no pdbs, assemblies on disk). I believe there is work schedule for VS2015 to support this.,

[MihaMarkic]

Hi Bill,

Hopefully they enable E&C in the future, needless to say that it is very useful.

[BillHiebert]

I checked and it is on the debugger teams backlog .

[MihaMarkic]

Great, thanks.

[hcapp01]

I am missing this feature so much. This is among a few things that c# can do better than nodejs

[Suchiman]

Me and my co-workers are missing this feature too, it's a painful loss in case you're wondering about priority. Bothers me as much as dropping xproj and hacking (because preserveCompilationContext) ASP.NET Core into csproj...

[j0nscalet]

Any updates on this? Seems like this will be available in RTM?

According to #14 there's been some work done.

Thanks!

[webtools-bot]

The GitHub Issue Tracker for the aspnet/Tooling repo is being deprecated in favor of Visual Studio's Report a Problem tool.

If this issue is still a problem with the RTW release of Visual Studio 2017, please report a new issue using the Report a Problem tool. While you can still use .NET Core and ASP.NET Preview tools with Visual Studio 2015, Visual Studio 2017 is now the officially supported tool for developing .NET Core and ASP.NET Core projects.

By using the Report a Problem tool (available in both VS 2017 and VS 2015), you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks. See Visual Studio's Talk to Us page for more details.

Please use the discussion topic here for feedback and questions on the deprecation of this issue tracker. Thanks!