Re: Saving breakpoints

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

On Sep 26, 3:32 pm, "MikeD" <nob...@xxxxxxxxxxx> wrote:
However, if you need to preserve "breakpoints", I recommend you add
Debug.Assert statements into your code. You can also use the Stop statement
to enter into break mode, but you must be very (VERY) careful to remove them
because Stop statements will terminate your compiled program, whereas
Debug.Assert statements don't even get compiled (with one exception, consult
VB's Help for more info).

--
Mike
Microsoft MVP Visual Basic

Thanks for your reply, Mike!
Unfortunately, adding a Debug.Assert is not an option. Since I am
whitebox-testing the code, it must not change during the course of the
test. Plus, my self-written add-in that guides me to the code lines I
need to test is line-number based, I would cause myself some extra
grief if I added code lines.

The strange thing: I once considered to add a breakpoint save/restore
into my own add-in. Back then, I couldn't find any interface to access
breakpoint data of the IDE.

Robert
.