I apologize for something that must be answered dozens of times elsewhere -- but after over an hour of searching haven't found any guidance on how to replace the old, legacy SolPartMenu menu system with the shiny new Nav one. Many references indicate to use the new one, but I haven't stumbled on a guide for moving a page from one to the other.
The 'pinned' docs discuss what controls are available in the new NAV control, but I've yet to find a guide or instructions for how to start using the new system!
Do I just replace the old line in my *.ascx skins:
<%@ Register TagPrefix="dnn" TagName="MENU" Src="~/Admin/Skins/SolPartMenu.ascx" %>
with:
<%@ Register TagPrefix="dnn" TagName="NAV" Src="~/Admin/Skins/Nav.ascx" %>
And then start debugging any issues I find by trial and error?
Some sources I've found (but none are comphrensive and only the first is presented as a guide):
www.dotnetnuke.com/Development/Forge/ModuleReports/tabid/970/EntryId/444/DNNMenu-Release-Announcement.aspx whereJonHenning introduces DNNMenu as SolpartMenu's replacement with why it is superior.
Jon Henning's great video:
www.dotnetnuke.com/Community/Blogs/tabid/825/EntryId/1874/New-Video-Available-Demonstrating-New-CSS-Capabilites-in-DNNMenu-v2-0.aspx Click on the Code EndevoursWebcast button near the top, or select:
http://blip.tv/file/get/Codeendeavors-UtilizingNewCssFeaturesInVersion20OfTheDotNetNukeMenu778.wmv
This video is probably the best, but focuses on the new system's additional features and specifically how to update the CSS stylesheet - from SolPartMenu,but doesn't go into that else might be affected or what fundamental changes are required first.
Jon Henning's DotNetNuke Navigation Controls, PreRelease Version (from 2005, but supposedly updated in 2009, and foundon the WebControls project download page - www.dotnetnuke.com/Products/Development/Forge/CoreWebControls/Downloads/tabid/874/Default.aspx) seems to be the most recent doc, and indicates what needs changing when going from
"the existing SolpartMenu skin object has a lot of value pre-defaulted. A simple declaration of the skin object like this
<dnn:MENU runat="server" id="dnnMENU"/>
will have an equivalent in the Nav control of this
<dnn:NAV runat="server" id="dnnNav" CSSControl="MainMenu_MenuBar"
CSSContainerRoot="MainMenu_MenuContainer" CSSNode="MainMenu_MenuItem"
CSSIcon="MainMenu_MenuIcon" CSSContainerSub="MainMenu_SubMenu"
CSSBreak="MainMenu_MenuBreak" CSSNodeHover="MainMenu_MenuItemSel"
CSSIndicateChildSub="MainMenu_MenuArrow" CSSIndicateChildRoot="MainMenu_RootMenuArrow"
PathSystemImage="[APPIMAGEPATH]" PathImage="[HOMEDIRECTORY]" MouseOverDisplay="highlight"
ProviderName="SolpartMenuNavigationProvider"
NodeLeftHTMLBreadCrumbRoot="<img src='[APPIMAGEPATH]/breadcrumb.gif'>" />
As you can tell the SolpartMenu skin object was defaulting a lot of CSS class names,
paths, and HTML.
www.dotnetnuke.com/Community/Blogs/tabid/825/EntryId/2393/Recommendation-for-DotNetNuke-Navigation-WebControl.aspx
- Cuong Dang 's blog is great but needs to provide instructions for getting started! HOW?!
www.dotnetnuke.com/Community/Forums/tabid/795/forumid/-1/threadid/207384/scope/posts/threadpage/4/Default.aspx is a good discussion, but presents more questions than it answers.
www.dotnetnuke.com/Community/Forums/tabid/795/forumid/77/threadid/249195/scope/posts/Default.aspx mentions using 3rd party modules to do this,
www.dotnetnuke.com/Community/Forums/tabid/795/forumid/109/threadid/85554/scope/posts/threadpage/3/Default.aspx hasa great post from Jon Henning, on 11/20/2006(!) about this. He states:
"The Nav skin object may be used with any navigation provider. Your choices in navigationproviders are Solpart, DNNMenu, DNNTree, DropDownList, and ASP2Menu." and more. This seems to indicate I (and others) are mixing up apples and oranges.
Sorry if this is so simple it doesn't need explaination, is explained elsewhere, or if I appear unappreciative for all the massive work that has made all this possible.