When the user selects a single page deep within the site, We would like to show them their current position and, at the same time, make it easy to move back up the hierarchy to any point. They will have a TreeView, of course, but we don't think that a tree is as clear and easy as a horizontal list of past locations. So, We decided that We would create a breadcrumb control in Windows Forms.

When you are looking at the code sample, you'll notice that my control is called an "Eyebrow" instead of a breadcrumb. Eyebrow is the name used in MSDN code, and it just stuck in my mind. You're probably wondering how this control relates to an eyebrow. So are we. We know my eyebrows don't have any information about my current position, and they certainly don't help us get around, but that's what they're called in the code, so that's how it'll be.

Back to the control. The control works by being associated with a TreeView. You can configure that association programmatically or through the property grid in Visual Studio^® at design time. The control's rendering is then based on information in the associated TreeView, namely the currently selected node.

By hooking the tree's selection changed event (AfterSelect), the control is notified whenever it needs to be redrawn. The associated TreeView is accessed directly to find the currently selected node, to navigate up through all of the parent nodes, and to change the selected node when the user clicks on one of the hyperlinked items. By obtaining all of its navigational information from the TreeView, the breadcrumb control doesn't have to know anything about your particular application. As long as you set up and populate your TreeView and handle the tree's events, this control should work within your application.

Full Article here