DotNetNuke vs. ASP.NET 2.0?
-
After working on my first from-the-ground-up asp.net 2.0 site, it seems like a lot of the big selling points of DotNetNuke are now baked directly into the .NET framework. -The new login providers & controls suite, mean all 3rd party controls can integrate with your site (i.e. forums control) -ASP.NET 2.0 Theming & Master Pages do a little bit better a job managing content areas than DNN. Youre not restricted to DNN's Top Pane, Left Pane, ContentPane etc.. for instance on my ASP.NET 2.0 site - the title and keywords of every webpage are simply seperate content areas in the master page, so every page on the site can use the master page and still have full control of keywords and title -The System.Sql.Common allows you to write provider indepentant code, in a much easier fashion. And Nullable is great for gettings dates from the database. (I'm sure DNN will start using this stuff too) -Sitemaps provide a map of your site. Usefull for make dynamic menus based on your sites content. So, are the 2 codebases offerring overlapping functionality? seems like it. One thing ASP.NET 2.0 is missing - is a portal manager that uses ASP.NET API's ONLY and ties everything together. Membership is already there, and themeing too. So all that is missing is a web based layout editor like that of DNN. If it targeted direct ASPX controls (instead of DNN's "Modules"), you wouldnt have any layout restrictions. Most importantly, it would simplify the development of 3D party controls. To add new "modules" to a site - just drop a dll in the bin folder and place them on a page. I dont want to knock DotNetNuke, but they really should look at cleaning up their code for their ASP.NET 2.0 release. Including rethinking their one .aspx page approach. It takes a higher demand on the database for things that in a regular web app would be compiled directly into the application. (i.e. it has to query what content to put on pane, and then all the reflection). If that information were compiled it would run way faster, without any loss of features. Anyway I'd love to hear what you guys think. If only I had more time, I'd code something up myself ;) 60% of statistics are made up on the spot -- modified at 19:04 Friday 4th November, 2005
-
After working on my first from-the-ground-up asp.net 2.0 site, it seems like a lot of the big selling points of DotNetNuke are now baked directly into the .NET framework. -The new login providers & controls suite, mean all 3rd party controls can integrate with your site (i.e. forums control) -ASP.NET 2.0 Theming & Master Pages do a little bit better a job managing content areas than DNN. Youre not restricted to DNN's Top Pane, Left Pane, ContentPane etc.. for instance on my ASP.NET 2.0 site - the title and keywords of every webpage are simply seperate content areas in the master page, so every page on the site can use the master page and still have full control of keywords and title -The System.Sql.Common allows you to write provider indepentant code, in a much easier fashion. And Nullable is great for gettings dates from the database. (I'm sure DNN will start using this stuff too) -Sitemaps provide a map of your site. Usefull for make dynamic menus based on your sites content. So, are the 2 codebases offerring overlapping functionality? seems like it. One thing ASP.NET 2.0 is missing - is a portal manager that uses ASP.NET API's ONLY and ties everything together. Membership is already there, and themeing too. So all that is missing is a web based layout editor like that of DNN. If it targeted direct ASPX controls (instead of DNN's "Modules"), you wouldnt have any layout restrictions. Most importantly, it would simplify the development of 3D party controls. To add new "modules" to a site - just drop a dll in the bin folder and place them on a page. I dont want to knock DotNetNuke, but they really should look at cleaning up their code for their ASP.NET 2.0 release. Including rethinking their one .aspx page approach. It takes a higher demand on the database for things that in a regular web app would be compiled directly into the application. (i.e. it has to query what content to put on pane, and then all the reflection). If that information were compiled it would run way faster, without any loss of features. Anyway I'd love to hear what you guys think. If only I had more time, I'd code something up myself ;) 60% of statistics are made up on the spot -- modified at 19:04 Friday 4th November, 2005
-
Hi there, take a look on this Master Page << >>