So I changed the Breadcrumb Register line to:
<%@ Register TagPrefix="dnn" TagName="BREADCRUMB" Src="~/DesktopModules/BreadCrumb/BreadCrumb.ascx" %>

Problem is, I don't see anything different. The control looks the same. When I got from Home to x and from x to y, I expected it would look like

..:: Home » X » Y ::..

but it only looke like that if that is the menu hierarchy. It looks like this now

..:: Home » Y ::..

Do I need to do something else?

Yes, in the Readme.txt file (in the PA) it defines the follow parameters:

+ Seperator (String) - HTML to use for the Seperator between tab names.
+ CssClass (String) [SkinObject] - Name of CSS class to use for styling the tab names.
+ BreadcrumbType (BreadcrumbTypeEnum) [Standard(0) | StackBased(1)] - How to create the tab path.
+ MaxTabCount (Integer) [5] - Maximum number of tab names to show in the object
+ AddToStack (Boolean) [True] - Whether or not to add this tab to the stack
+ ClearStack (Boolean) [False] - Whether or not to clear the stack when landing on this tab

Stack Based:
When the Breadcrumb is configured to be Stack based, then it acts as a true breadcrumb, showing
the complete path taken from the last time the stack was cleared. Clicking the tab name for
navigation will automatically pop it and the other tabs on top from the stack. A session
variable called 'bi4ce_bc_back' is publically available with the full URL that is at the top
of the stack (last visited tab), including the full query string.

An example for what you are attempting would be this:

<dnn:BREADCRUMB runat="server" id="dnnBREADCRUMB" RootLevel="1" AddToStack ="True"/>

You may find it useful to have a skin setup that clears the stack

So I am getting the idea that I need to do more than change the Register line.

The readme file says look at the ListX configurations for http://dev.bi4ce.com/Northwind. Which I would love to do, except I don't know how to see the ListX configurations.

I also don't know where to put the example <dnn:breadcrumb...> that you put in your reply.

I'm also now concerned that I need to have another skin that clears a stack. This seems way over my head.

Are there any examples of this working some where?

Thanks...

Hi Larry-K,
I dont think you need a new skin to handle the breadcrumb. All you really need to do is modify the dnn:Breadcumb in the current DNN skin you are working with. It should be one tag that is near the top of the skin. If it is not there you can copy and paste the example kevinmschreiner put above and play with it a bit by modifying the attributes for the tag.

The breadcrumb can actually go anywhere in the skin. Feel free to move it around a little to see how placing the tag in the skin effects the position of the breadcrumb when the page loads.

Unfortunately the Readme.txt did not include an example on how to use the dnn:Breadcurmb. We will be putting that in the next release of the product.
Thanks,

That did work, once I added BreadcrumbType="1" and changed RootLevel to 0 (which is what is was in the release skin).

Do I need to have a version of the skin so the home page can have ClearStack="True"? And if that is true, how do I make a copy of a skin?

Hi Larry,
You can certainly copy skins as many times as you want. The best way I have found is to copy and rename the aspx file to a new name. Then, on the setting for the tab you can select the new skin. The DNN system can read the skins directory under _default to know exactly which skins you could apply.
Thanks,

I was trying to determine if the "Correct" way (or should I suggest the way that r2integrated would do it on one of their sites). You are the experts, and I am trying to do this the right way so I don’t have to keep dealing with it.

So far, I can see two ways to do this (and there are probably others I am missing). Would you recommend that I use 2 skins, one for the home page and one for all the others? Or would you recommend that I just need one skin, and the ClearStack=”True” isn’t really needed on the home page? Or is there a different better answer that I am missing.

Thanks for helping me understand how this should be done.

Generally we develop this with multiple skins, depending on the client. For nearly all sites the Home page differs in format from the inner pages because the main landing page is generally more visually interactive than the internals. With this - when we used the Stacked approach, we always have the home skin set to ClearStack because we want it to always say "Home" by itself. We often do this for major level 2 pages also, depending on the site and structure. In general - we often have 3 skins per site. A Home skin - which often has 3 columns or more. An internal skin which generally has 2 columns. And a content skin - which is one column.