DotNetNuke Case Study: DNNTreeView for Large DNN Applications

Posted by: Joe Brinkman, on 01 Jun 2009 | View original | Bookmarked: 0 time(s)

When deploying large DotNetNuke applications, you may consider using a custom menu that allows granular access to individual module controls. This will allow you to still group and deploy collections of controls as module packages yet present each individual control as a separate page to the end user. The Problem I recently ran into a long time DotNetNuke developer who indicated that a recent large DNN site he deployed had to be converted to MVC because it could not take the user load. I have...

Advertisement
Free Agile Project Management Tool from Telerik
TeamPulse Community Edition helps your team effectively capture requirements, manage project plans, assign and track work, and most importantly, be continually connected with each other.
Category: DotNetNuke | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 816 | Hits: 15

Similar Posts

  • Hello India! more
  • Searching for the "Holy Grail" of Menu Item Customization more
  • Look Mom - No Hands more
  • DotNetNuke WebControls v1.5 Released more
  • DotNetNuke vs. SharePoint - SharePoint Wins more
  • Performance Enhancements more
  • Web Application Projects more
  • Joel Spolsky: Indigo won't enable a new class of applications more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD