Is there some way to tell the debugger not to stop at WndProc?

  • Thread starter Thread starter Franky
  • Start date Start date
F

Franky

when I'm debugging (single stepping) I keep getting to WndProc which I do
not want to step through.



Is there some way to tell the debugger not to stop at WndProc?



Thanks
 
Thanks just what I need

In the debugger I know about F5, F10 and F11

I've been looking in Help - I don't know where they are documented.

What I'm looking for is a F key that would move me through a routine once
I'm in it. Is there one?

Thanks again
 
Ctrl-Shift-F8 (Step out).


Franky said:
Thanks just what I need

In the debugger I know about F5, F10 and F11

I've been looking in Help - I don't know where they are documented.

What I'm looking for is a F key that would move me through a routine once
I'm in it. Is there one?

Thanks again
 
After I posted that I keep looking and thought I found on the internet that
shift-F11 did that.
I'll now have to find out what is different about shift-F11 and
Ctrl-Shift-F8

Thanks
 
I found a site that listed keys for VS (including F11) and keys for VB
(including F8)
 
Franky said:
After I posted that I keep looking and thought I found on the internet that
shift-F11 did that.
I'll now have to find out what is different about shift-F11 and
Ctrl-Shift-F8

I think the difference is how you have your editor set up.
Ctrl-Shift-F8 is the control scheme use by VB6 and carried over into
VB.Net. Whereas the Shift-F11 is probably a carry over from Visual C.
In the settings you can set up your profile as a VB developer or C#
developer and that affects the default key mappings. Of course, you
can change any command to any keystroke combo you want.

Chris
 
That explains it. Some of the options are VB6, C#2005 and (Default)

I'm using (Default) and use F5, F10, F11 and now Shift-F11.

I don't remember what I used for VB6 but I do remember having to adapt after
moving to VS2003 so it was probably not F10 and F11.

Thanks

and thanks Robinson
 
Back
Top