Stepping through the IDE

I'm a former VB programmer now leaning some C#, and I've noticed that when I step through my code using F11 (Step into) the debug trace does follow the actually executed code all the time, for instance:

private void tvw_source_AfterCheck(object sender, System.Windows.Forms.TreeViewEventArgs e)
{
MessageBox.Show(e.Node.ToString());
SetCheck(e.Node,e.Node.Checked);
}

private void SetCheck(TreeNode node, bool check)
{
// find all the child nodes from this node
foreach (TreeNode n in node.Nodes)
{
n.Checked = check; // check the node - recursive call back to AfterCheck
}
}

If I click on the Root node and place a break at n.Checked = check and then step through, the stepping never goes to the AfterCheck delegate, but it executes the code as verified by the MessageBox ... ... is there an issue with Debug in .NET 2003 - or am I doing something wrong... I'm very perplexed as VS6 never did this. :S

Thanks in advance.

Sorry to be a bore, but is it only me that's experiencing/experienced this?

I may try and package up the source and attach it so one of you considerate souls can confirm the failure for me. ;)

Did you create the Eventhandler for the Aftercheck Event?

Code:

---

this.treeView1.AfterCheck += new System.Windows.Forms.TreeViewEventHandler(this.treeView1_AfterCheck);

---

Yes. As I said, the code runs... my point is when I single step through it, the stepping doesn't go to the code.

It is probably because a delegate is a method instance and so you are not actually executing the method itself, but an instance of it. Logical, but it should step through it anyway. VC# 2005 (Express) does, so it may have been an issue with 2003 that was fixed in '05.

If you're right, it's a very big issue as far as debugging is concerned. :S It's still an executed area of code whether it be part of an instance or class. :(

Can you zip and post the project?

Attached, mate.

It steps through the handler fine, but you have to place a breakpoint on the first line. It seems that '03 only steps through the current method.

Ugh!

Yeah, I noticed it was ok when I put a breakpoint there... but assumed I could step through the whole execution path once broken at a point.

That's really sucky, especially when dealing with handlers that may not have an immediately identifiable execution path. :(

At least it's not just me.