Visual Studio and .NET Framework Home
Edit and Continue is not working in x64
as By Design
7/11/2008 7:26:48 AM
The edit and continue function in VB is not working while debugging in AnyCPU or x64 target on a x64 machine.
Visual Studio 2008
Windows XP Professional
Operating System Language
The edit and continue function in VB is not working while debugging in AnyCPU or x64 target on a x64 machine
Enable this functionality on x64
TAP Code (if applicable)
You can indicate your satisfaction with how Microsoft handled this issue by completing this quick
3 question survey
to post a comment.
Please enter a comment.
on 6/24/2011 at 6:43 PM
Votes should be summarized.
on 10/18/2010 at 8:05 PM
"It requires updates to many different components of Visual Studio including the debugger and the Common Language Runtime."
That sounds like an explicit decision to omitt it when the CLR and debugger were made in the first place. Microsoft please step up and support the developers who support you.
on 3/4/2010 at 9:11 AM
EnC support for 64Bit would be nice, but I would never switch to x86 target for using EnC.
on 12/3/2009 at 3:14 PM
I am developing .net since beta 1.0. In the pre beta of .net 1.0 we had Edit and continue! In Beta 2 this function was removed. So I had to wait for .net 2.0.... Since we are developing software with many plugins for 3rd party software we are very happy getting EnC in C#. (bad documentation, long startup times and use cases to reach the bug...). With EnC I am able to increase my productivity about 20%. Some 3rd party software producers have x86 and x64 versions of ther software. On a x64 OS only the x64 version could be installed. So I have to debug in x64 mode lossing EnC. This stops me using x64 OS!!! I would loss 20% of my productivit. But as I have seen last weekend, nerly all new consumer laptops come out of the box with WIN7 64!. We need testing our app on x64 too.
PLEASE only release VS2010 with EnC. (VS2011 with EnC would be better than VS2010 without EnC)
on 10/20/2009 at 3:06 AM
...and for anyone who is equally horrified about the insane descision to default all new projects to 32-bit, please also vote on these bugs:
on 9/24/2009 at 4:04 AM
Forcing us to switch to targeting legacy x86 in order to get the edit and continue experience we've all come to expect is a truely awful workaround.
64-bit E&C support should have been a top priority for .NET 4/VS2010, especially considering the number of requests on Connect dating back almost half a decade for this.
What's more, it's absolutely despicable that there are plans to default all new projects in VS2010 to target 32bit only (as opposed to the platform adaptive Any CPU).
on 8/8/2008 at 11:01 AM
Thanks for your feedback. Edit and continue support for 64-bit is a known hole in the Visual Studio debugger and something we will try to address in the future. It requires updates to many different components of Visual Studio including the debugger and the Common Language Runtime.
For now our suggestion is to switch from "Any CPU" to "x86" during your design phase in order to use the edit and continue features.
to post a workaround.
Please enter a workaround.
© 2014 Microsoft