By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,246 Members | 1,515 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,246 IT Pros & Developers. It's quick & easy.

Debug Step into another form

P: n/a
Hi everyone, i'm workin with vb.net 2003 and i using the debug step into, but
when i call a form within another the debugger doesn't go to the form that i
call, how do i solve this, without putting a breakpoint.

SC.
Oct 8 '07 #1
Share this Question
Share on Google+
5 Replies


P: n/a
"SC" <SC@discussions.microsoft.comschrieb
Hi everyone, i'm workin with vb.net 2003 and i using the debug step
into, but when i call a form within another the debugger doesn't go
to the form that i call, how do i solve this, without putting a
breakpoint.

Debug into what? Which method of the Form do you call?
Armin
Oct 8 '07 #2

P: n/a
i just want to debug step by step in a form, but when i call some other form
with the sentence:

form.ShowDialog()

the debug cursor doesn't navigate to that form, i mean only when i exit that
form the debugger starts again.

--
Saludos,
SC
"Armin Zingler" wrote:
"SC" <SC@discussions.microsoft.comschrieb
Hi everyone, i'm workin with vb.net 2003 and i using the debug step
into, but when i call a form within another the debugger doesn't go
to the form that i call, how do i solve this, without putting a
breakpoint.


Debug into what? Which method of the Form do you call?
Armin
Oct 25 '07 #3

P: n/a
"Sergio Cifuentes" <Se*************@discussions.microsoft.comschrie b
i just want to debug step by step in a form, but when i call some
other form with the sentence:

form.ShowDialog()

the debug cursor doesn't navigate to that form,
ShowDialog does not belong to your source code, hence the debugger can not
step into it. You could only step into the disassembly, but the method is
part of the Framework and not of your project.

The debugger can only stop at executable lines. In which line do you want it
to stop?

i mean only when i
exit that form the debugger starts again.

Armin

Oct 25 '07 #4

P: n/a
Thanks Armin, what i want is to follow all the program logic since the error
is in logic, i guess i'll have to put some breakpoints isn't it?

the error is in the second form, my first form is a login form, so if i
debug with the step into i only debug my login form, and what i want is to
debug the second form.

--
Saludos,
Sergio Cifuentes
"Armin Zingler" wrote:
"Sergio Cifuentes" <Se*************@discussions.microsoft.comschrie b
i just want to debug step by step in a form, but when i call some
other form with the sentence:

form.ShowDialog()

the debug cursor doesn't navigate to that form,

ShowDialog does not belong to your source code, hence the debugger can not
step into it. You could only step into the disassembly, but the method is
part of the Framework and not of your project.

The debugger can only stop at executable lines. In which line do you want it
to stop?

i mean only when i
exit that form the debugger starts again.


Armin

Oct 25 '07 #5

P: n/a
"Sergio Cifuentes" <Se*************@discussions.microsoft.comschrie b
Thanks Armin, what i want is to follow all the program logic since
the error is in logic, i guess i'll have to put some breakpoints
isn't it?

the error is in the second form, my first form is a login form, so
if i debug with the step into i only debug my login form, and what i
want is to debug the second form.
Unfortunately, in VB 2003, you have to set breakpoints.

In VB 2005, you can set a breakpoint at ShowDialog. Then, when you press F8
(or whatever key is single step in your IDE), the IDE stops at any source
code line that is first executed in the Form.
Armin

Oct 25 '07 #6

This discussion thread is closed

Replies have been disabled for this discussion.