I'm posting this here as it sounds like this is the correct thread. However, if not, I can repost this in the 3.1 beta thread.

I'm glad to see that we have the option to use best-practice when rendering Navigation Menus. However, I don't see how the design allows for this when using the new Skinning Objects.

I'd need to specify "custom attributes" as well as including an assembly?

<object id="dnnNAV" codetype="dotnetnuke/server" codebase="NAV">

    <param name="ProviderName" value="DNNMenuNavigationProvider" />

    <param name="CSSControl" value="dnnNav" />

    <param name="RenderMode" value="UnorderedList" />

</object>

Here is the code from the .ascx file I would like to recreate

<%@ Register TagPrefix="dnn" Namespace="DotNetNuke.UI.Skins" Assembly="DotNetNuke" %>

...

<dnn:NAV runat="server" id="dnnNAV" ProviderName="DNNMenuNavigationProvider" CSSControl="dnnNav">

   <customattributes>

        <dnn:customattribute value="UnorderedList" name="RenderMode" />

    </customattributes>

</dnn:NAV>

I don't have the answer to your question - and no-one has been able to answer this for me all to well...

Can we resolve the whole NavMenu Unordered List thing once and for all, please...?!  Using Navsuit, Snapsis or HouseMenu is just not cutting it.  If frameworks like (dare-I-say-it) WordPress and Yola can get it right, why can't the framework that I prefer do it...  It's the menu for goodness sake!  The primary means of navigating a site...  There's nothing semantic or intuitive about Solpart (stop using it guys) or Nav.

Com'on!

Your thoughts... help... and guidance will be appreciated.  Maybe a permanent post on the subject - like the skinning guide post - would help.

Jon

Shebang Websites - A product of Mogridge Design
Hey, we're partnered with UntangleMyWeb.com

k, Jon, I noticed, you have been quicker ;)