VB.NET 2005 Interactive Debugging/Editing Limitations

[Anonymous]

I'm trying to pin down when VB.NET can/can't do debugging/editing. It
seems as long as the Active Configuration is set to Debug I can set
breakpoints, walk through, set watches, etc.

However the next level is what I'm curious about. When the debug
external program is 32bit AutoCAD, I can stop the execution and actually
change the code while its executing as long as its 'top level' code.
Whenever the code steps into subs/functions in another .VB file (perhaps
its in a referenced module), I can't seem to edit there. I also can't
seem to stop and edit AT ALL in 64bit AutoCAD.

Are there any documented procedures on how/when this is supposed to
work? Anyone having similar experiences?

Thanks in advance,

Terry

[Anonymous]

Terry W. Dotson wrote:

> I'm trying to pin down when VB.NET can/can't do debugging/editing.

Okay I've found at least a partial answer to my own question in case
anyone is interested. If I'm not mistaken, code in a *linked* file
cannot be changed during the debugging process whereas code in a normal
file can.

Nothing like being able to edit the code while debugging. 🙂

Terry