This post originated from an RSS feed registered with .NET Buzz
by Brad Wilson.
Original Post: ASPnetMenu
Feed Title: The .NET Guy
Feed URL: /error.aspx?aspxerrorpath=/dotnetguy/Rss.aspx
Feed Description: A personal blog about technology in general, .NET in specific, and when all else fails, the real world.
Peter Provost posts about ASPnetMenu, a product we purchased and are now in the process of replacing. The problem we had with this control was that the HTML output was quite copious, and even moderately large menus (with a few dozen items) would end up being many 10s of K of HTML. Part of the problem is that they used tables for layout; another part is simply inefficient HTML (each menu element has 4 or 5 events tagged off of it).
Since menus don't often change, it's best to get a system where your menu is entirely in JavaScript. Then you can emit the menu as a separate URL, with separate caching semantics from your menu-adorned pages. To that end, we think we're probably moving to AJMenu from NavSurf. It's not .NET-based, but it should be easy to make a .NET wrapper that could dynamically generate the JavaScript as needed.
Hey Brad, how's it going? I read your message and thought you might be able to help me. Your help would greatly be appreciated.
I've been asked to explore the limitations (if any) of the ASPnetMenu for immediate use within our work environment, a non-profit organization. We presently have an in-house internet services team that has a limited programming background, utilizing Dreamweaver to edit existing files and updates.
Resources are limited and clean-up of present site is in effect. We're looking to standardize menu's within the organization create a polished looked without complex back-end coding to support moderate modifications.
Please let me know your thoughts integrating ASPnetMenu with Dreamweaver functionality?
Previous Topic
