Why Debugger won't let me edit and continue
- Okay,
So, i've been debugging with VS for some time now, and when I have two projects open, a DLL Class Assembly, and an EXE application, I used to be able to step into source from the DLL, and Edit and Continue in the source files for the DLL. Now granted I was having some weird configuration glitches so I recent ran a reset settings on VS, but isn't Edit and continue default? Why won't it allow me to edit the dll source files while debugging like it used to?
Thanks
Jaeden "Sifo Dyas" al'Raec Ruiner
"Never Trust a computer. Your brain is smarter than any micro-chip."
Všechny reakce
Hello,
Yes, Edit and Continue feature is enabled in default. In .NET 2.0, we focused managed Edit and continue resources on the core-scenarios. However, there are some non-core scenarios in which we could not edit and continue:
1. for non-x86 platform.
2. if a third-part profiler is attached.
3. dynamic code or in-memory modules
4. if we're interop-debugging
5. code loaded by NGen
6. for the mscorlib.dll assembly
These are limitations of the CLR, not the Visual Studio's fault.
Please refer to this link for more explaination: http://blogs.msdn.com/jmstall/archive/2006/02/13/cant_do_enc.aspxBased on your previous post, here are my suggestion:
1. Please open Tools->Options...->Debugging->Edit and Continue, make sure Enable Edit and Continue option has been checked.
2. Please check the Environment Variables, if there are any one named COR_ENABLE_PROFILING, COR_LINE_PROFILING, or COR_GC_PROFILING, then, set their values to 0
3. Please run Visual Studio in safe mode by entering devenv /safemode in Visual Studio 2008 command prompt.Best regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback, please tell us.
Welcome to the All-In-One Code Framework!- I'm not sure if i'm doing any of those.
None of those Environment Variables exist on my system. Edit & continue is activated. I haven't changed anything in the IDE at all, and previously I was able to edit during a breakpoint in the DLL (my own class library project). Granted, Lambda expressions and LINQ statements prevent the editing of a method during edit & continue, but currently every source file in my class library is locked readonly, even though nothing changed (that I'm aware of).
J"SD"a'RR
"Never Trust a computer. Your brain is smarter than any micro-chip."
I'm having(probably) the same issue.
I'm using VS 2005, with WinForms code. I used to be able to Edit and Continue all over the place, and now, in some projects, I can't type in the code window. I can 'technically' Edit and Continue, because I can select and drag code around, but I can't enter any keystrokes into the text editor.
I've tried all the suggestions about making sure the Edit and Continue is on, Break all Processes, Optimize code is off, Debug symbol generation is set to full.
Is there any chance this is related to source control? The project that is not allowing me to type while it's executing is under source control(Surround SCM w/VS plugin), but the file in question is checked out and not read-only. The only reason I bring that up, is that have no problem with edit and continue in another solution which is not under source control.
Anyone have any ideas?- UPDATE: I can also Undo/Redo while the code is executing, and these changes are executed live, like E&C changes are supposed to be. But still no new keystrokes allowed. The fact that I can make live edits leads me to think this isn't a debugger issue, but a bug in the IDE.
- UPDATE: Ok, I don't like this, but it looks like it has something to do with Resharper, or Addins in general. I'm running Resharper 2.5, and when I disable it, the problem goes away and I can E&C just fine. The weird thing is, I was using Resharper on those other projects I mentioned, that weren't in source control, and E&C worked there. So maybe its a 3 way collision of E&C, Resharper and Surround SCM.
I had really gotten used to all these awesome tools, dammit.
