Ah - I certainly did not get that before.

I have no idea if there is a formal approved way of doing this, and I am no expert, but that won't stop me making a guess.

Choice 1 - probably easiest - if you can assume that all browsers will have javascript enabled

- The standard menu ultimately emits a bunch of nested lists. CSS styling gives it the menu/megamenu appearance.
- Arrange for your control to create a bunch of li elements that would style up the way you want
- Add a couple of lines of jQuery that will find the right place in the menu (you will likely have to hard code page names/tab numbers for this) and glue the li's into the rest of the menu structure.
- The menu styling takes care of the rest but if a browser has js off the user will see nothing.

Choice 2 - probably harder - but can work without js

- The standard menu uses xslt to transform some xml from the menu provider into the nested lists.
- Either work out how to make the xslt merge your code's output into the rest of what it does (I suspect this is hard, because I *hate* xslt; and I have no idea how you get your code called)
- Or merge your control code into the menu's provider to create a custom provider. I have never done that, never looked at the code involved, and I *still* suspect it might be easier than working in the xslt. So your custom provider does what it likes - createing extra xml elements; the xslt takes it on trust and creates lists; the page styling shows them in the page.

---

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk

Maybe have a look at the razor tempates concept - it gives you very detailed control over where and how each menu element is injected.

http://www.dotnetnuke.com/Resources/W...

Westa