On Fri, 27 Apr 2007 13:49:06 -0700, Zytan <zy**********@gmail.comwrote:
Ok, so the full version allows editing the code while the code is
running in the debugger? I want to be explicit, to make sure we're
talking about the same thing.
I am not looking to use Edit and Continue. I just want the code to
run, and when I notice something wrong, I'll go to that file, and
start typing, and let the program continue to run without pausing it.
Oh. No, I don't know if you can do that in any version of Visual Studio.
I don't think so, since VS (if I recall correctly) locks the source code
while the program is running, and if you edit it while it's paused assumes
you want to "edit and continue". Frankly, I think this is the correct
behavior...what happens if you continue the program, but either because of
an exception or because you broke into the debugger again the instruction
pointer winds up in the code you've been editing? While it would be
theoretically possible for the IDE to track your changes and correlate
them to the PDB, it seems to me that for nearly all programmers allowing
that would just lead to a huge amount of confusion (and way too many
support calls :) ).
Of course, you could just use a different editor and reload the source
file in Visual Studio when you're ready to rebuild. Then VS doesn't have
to deal with source code that doesn't match the running code.
Do you know of ANY development environment that does what you're asking
about here?
Pete