With VB6, you were able to break the program at any point, perform a "Step Into" to go into line-by-line debugging mode until another event fired, at which point you could step through each step of the code. Can anyone tell me how to do anything equivilant to this with VB.NET? Stepping into a "Break"'ed program does not seem to work even remotely the same way with vb.net..
Thanks for any help!

I'm not too familiar with vb6 and "Step Into", but with vb.net you use "Breakpoints" to debug a section of code.

That was possible with VB6 as well... The method I'm talking about seemed to treat each line of executable code as having a breakpoint during each "step into" the code.

Hi there,

It is still called Step Into in VB .NET.

Set a breakpoint somewhere, press F5 to start your application and wait until it hits the breakpoint. Then use F11 (Step Into) to step through your code line by line.

Is this what you meant?

Imar


---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

Yes & No.. Here's an example of what I'm referring to:

2 buttons on a form, with the following code:

Private Sub Button1_Click (ByVal sender as System.Object, ByVal e as System.EventArgs) Handles Button1.Click
     ' Breakpoint on the next Messagebox.Show("")
     Messagebox.Show("")

End Sub

Private Sub Button2_Click (ByVal sender as System.Object, ByVal e as System.EventArgs) Handles Button2.Click
     ' NO Breakpoint on the next Messagebox.Show("")
     Messagebox.Show("")

End Sub

==========

Click Button1 -- You break into the code and start debugging.
Hit F11 to step into -- The messagebox appears
Hit F11 to step into -- You debug the "End Sub" line
Click Button2 -- No debugging of this sub happens.

In VB6, you would still be debugging whatever event fired after you "Step Into" past the "End Sub" line of Sub Button1 ...

Right, I see what you mean now.

In that case, I am afraid I don't know the answer.

Imar



---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

I have never had a problem stepping through a program in .NET- However, you can't debug while stepping through in .NET- you need to edit and restart in most cases.


Hal Levy
Web Developer, PDI Inc.

NOT a Wiley/Wrox Employee

nhdw-

The code you provided shows two different events. I think there is a problem (maybe it's a feature) in VS.net that doesn't allow you to "step into" the very beginning of an execution (like you could in older VB applications). This is what I have found in ASP.net at least. Haven't done a whole lot of debugging in non ASP.net VB.net. As Imar has suggested, you have to set a breakpoint at the point of interest, and only from that point forward can you step thru all parts of the execution. And even this is problematic. In ASP.net I have seen cases where I have put a break on the Page_Load function, but NOT on some event that I expect to fire after that. The debugger hit the Page_Load breakpoint, then I step thru all of that method. After "End Function" for Page_Load, "Step Into..." essentially becomes "Go". Unless you have another breakpoint on the other parts of your code (i.e. in the events), you are off and running without debugs stops. I think you'll need to put another breakpoint in the applicable event.

Peter
------------------------------------------------------
Work smarter, not harder.

Peter ... re: After "End Function" for Page_Load, "Step Into..." essentially becomes "Go".... That seems exactly like what's happening... It's a shame... the "Ongoing debug" while stepping into the code with VB6 was extremely useful & much simpler than setting multiple breakpoints throughout the program... Oh well :) If it IS a bug, hopefully it's fixed soon, but I'm not sure how many people use this kind of debugging...