I'm using Visual Studio 2008, C#. I try to use edit-and-continue (edit the code while debugging), and get this exception:
"Changes to 64-bit applications are not allowed"
Why is that? Is there a workaround?
I'm using Visual Studio 2008, C#. I try to use edit-and-continue (edit the code while debugging), and get this exception:
"Changes to 64-bit applications are not allowed"
Why is that? Is there a workaround?
when Target CPU is set to 'Any CPU', it will run as a 32bit application on a 32bit windows, and 64bit application on a 64bit windows. However visual studio does not allow 'edit-and-continue' feature for 64bit application.
In order to debug 'fluently' on 64bit machine, we can either:
a) set 'Target CPU' to 'Any CPU' but check the 'Prefer 32bit' box.
b) or, set 'Target CPU' to 'x86'
VERY important: both option requires the 'Enable optimizations' box to be unChecked.
I had the same error message in MS Visual C# Express 2010. It was funny though, because the application was definitely configured as an x86 Project!
In the end, it was the following line missing in my .csproj file:
I don't know why it was missing ... I guess MS Visual C# Express 2010 is not bugfree ;)
Like jcopenha said there's no edit-and-continue on x64 yet. Current version of the 64bit CLR does not support it. However, there's a work around.
You can find it on Bug Babble post.
Hope it helps.
The "Edit and Continue" feature for 64-bit code will be supported under Visual Studio 2013.
More information here.
Edit and Continue is not supported on 64 bit applications at the CLR level so there is no way for Visual Studio to implement it either.
The easiest way to work around this problem is to target your application to x86 chips. This will cause it to run in Wow64 mode as a 32 bit process and hence be able to ENC. You can do this by doing the following
Personally, what I actually want is stop-and-edit not edit-and-continue.
So I simply turn off Tools / Options / Debugging / Edit and Continue.
Doing so inhibits that pesky dialog box from pestering me about a missing feature I didn't want in the first place :-)