J
Jim Bancroft
Hi everyone,
I have a DLL and a console app I'm using together, both created in VB
..Net. I've added both projects to a Visual Studio solution, and have a
breakpoint set on my console app, where it calls a public method on one of
the dll's objects.
When I reach my console app's breakpoint and hit F11 to "step into" the
dll method, I just skip to the next line of the console app. That is,
unless I have a breakpoint set on the dll's method.
Is that behavior by design, or can I arrange things so that I don't need to
set breakpoints in ancillary projects when debugging my main app? Thanks
for helping me clear this up.
-Jim
I have a DLL and a console app I'm using together, both created in VB
..Net. I've added both projects to a Visual Studio solution, and have a
breakpoint set on my console app, where it calls a public method on one of
the dll's objects.
When I reach my console app's breakpoint and hit F11 to "step into" the
dll method, I just skip to the next line of the console app. That is,
unless I have a breakpoint set on the dll's method.
Is that behavior by design, or can I arrange things so that I don't need to
set breakpoints in ancillary projects when debugging my main app? Thanks
for helping me clear this up.
-Jim