Trying to debug a vb.NET application, I set a breakpoint, then try to move
forward from there.
While this has worked in the past (I often did this back in VB6.0), now most
often when I try to move forward, I get a NullReference exception, with the
green arrowhead at the beginning of the code for the form.
    How can I debug this?

    = Turtle

Mac,

Normally it should go with F11 (except when there is an error of course).
And a NullReference exception is probably one of the most you will see in
the beginning.

Therefore show a piece of code when that happens.

Cor

Thanks for writing back, Cor!

In VB6.0, I could usually get the code to break where the error is; that
made debugging much easier.
I've often been able to do that in VB.Net as well, but in this particular
application, it seems that I'm more and more frequently seeing that when it
breaks (even though code has clearly been running before the error), the
green arrowhead shows at the beginning of the form module.   What causes
this?  How can I tell where the error is?

- Turtle

Show quoteHide quote

Mac,

As I wrote before, can you show a piece of code where that happens, it is
not clear for me. I cannot remember me that I ever saw the behaviour that
you describe.

Cor

HTML Forms Progamatically Via VB.NET
Microsoft MVPs Say They Want Old VB Back
Problem with VS.NET 2003
the menu and the shortcuts
Problem Compare Two File
How to implement ComboBox.FindValue
list item colour
What is threading?
VB6 to VB.NET dlls
Cookies working on intranet but NOT working on Internet