Just to follow up a bit for benefit of lurkers and anyone searching for this later :
Today we wanted to understand exactly what happened when double-clicking on a row in a listview and briinging up an edit dialog ( the thing that piqued the curiosity was trying to understand why explicitly setting the pointer of the listviews BO to the instance on the edit form was necessary when coming to the edit form from a double-click but was not necessary when coming form a button that called the edit() and then showdialogue()
Once we determined the MouseDoubleclick of the listview (and not the doubleclick as we first thought) was the event that was handled, we put a stub method in the calling form
Private Sub lvEmployeeActions_MouseDoubleClick(ByVal sender As Object, ByVal e As System.Windows.Forms.MouseEventArgs) Handles lvEmployeeActions.MouseDoubleClickEnd Sub Put a breakpoint on the endsub. When the break came, the callstack showed the Microfour method which is being inherited
Doubeclick it in the callstack and you're off an running, can then step through a lot of framework code.
Of course, if you are moving through your code and hit a method (rather than an event handler ) you can just step in to get to the SF stuff
Hope this helps somebody else. A great way to start understanding (and appreciated) what the Microfourians have been up to