Learn to use Visual Studio, Visual Studio Online, Application Insights and Team Foundation Server to decrease rework, increase transparency into your application and increase the rate at which you can ship high quality software throughout the application lifecycle
You asked, and we have listened. When using the debugger, Edit and Continue for 64-bit targeted environments is something that many .NET developers wanted, and voted heavily for on the Visual Studio uservoice site. The good news is that with the latest version of Visual Studio, it’s here and you can now try it yourself.
Here is how to see it in action:
Consider the following line of code and imagine you are stopped at that line in the debugger (e.g. due to a breakpoint)
int ret = 5 * foo;
If you try to edit that code and specifically from foo to bar (int ret = 5 * bar;) while debugging in previous versions of Visual Studio, you would see this dialog
With VS2013, the dialog will not appear again, and instead you’ll be able to edit the code and continue debugging.
For people who are new to the Edit and Continue feature, Edit and Continue eliminates the need to stop and restart a debugging session when a developer makes modification to code being debugged. This feature exist for 32-bit targeted environments and with the latest version of Visual Studio it is now available for 64-bit. Please read online for more on the Edit and Continue debugger feature.
There are several ways that Edit and Continue helps the developer:
Note that some ASP.NET developers are not aware that support for Edit and Continue exists but requires developers to enable it first. This can be done by going to the project properties and under the web settings there is a checkbox you’ll need to check named “enabled Edit and Continue”. To simplify the workflow starting with Visual Studio 2013 the setting is turned on by default.
For Azure cloud tools developers there are two main options: web role and worker role. To enable Edit and Continue for web roles you’ll need to set your web role project to use IIS Express. Worker roles currently are not supported, however we will enable this in a future release.
In closing, we are really happy to bring this capability to you and as always your feedback is welcome in the diagnostics forum.
Can you please log an issue on connect.microsoft.com/VisualStudio
Someone will try to get a repro and more details. Since we don't have a repro now, it's hard to investigate
Doesn't work. As usual. "Changes are not allowed for this module as it was not built"
I understand your frustration and I'm sorry for the trouble this is giving you.
Can you, please, log a feedback item for us on connect.microsoft.com/VisualStudio? That way we can get your repro and investigate this.
If having enabled "Use Managed Compatibility Mode" because of issue with the debugger. Then one will still get the error "Changes to 64-bit applications are not allowed".
@ Rolf Kristensen
Enabling Compatibility Mode makes use of the old debugger engine, where Edit and Continue x64 isn't implemented, which is why you are getting the error.
What issue are you having - that you had to enable Managed Compatibility Mode for it?
It is working on Visual Studio pro 2012 update 4.
I have a simple Console App that I am working with and unable to use EnC.
VS2013 on Win7 Enterprise 64bit.
Any chance this will be addressed?