I am currently in the very early development and envisioning phase of what will be a very ambitious enterprise workflow application. My goal (isn't everybody's?) is to develop an application which uses and implements the best possible patterns & practices today. As the application will be a web-based application, it is a no-brainer for me to use DotNetNuke as the Enterprise Application Framework for hosting the application. Those reading this who may be familiar with DotNetNuke may be thinking that DotNetNuke is great for developing simple modules, and displaying relatively static content, but it's Data Access Layer/Business Layer is too simplistic for an Enterprise Grade Application, and I would agree with you completely if you thought that, which is why I am writing this in the first place. DotNetNuke is great at hosting an application, great at handling and managing user & role data, security and exception logging, content management functionality, and more, but it's data access ... Read More »
I am currently in the very early development and envisioning phase of what will be a very ambitious enterprise workflow application. My goal (isn't everybody's?) is to develop an application which uses and implements the best possible patterns & practices today. As the application will be a web-based application, it is a no-brainer for me to use DotNetNuke as the Enterprise Application Framework for hosting the application.
Those reading this who may be familiar with DotNetNuke may be thinking that DotNetNuke is great for developing simple modules, and displaying relatively static content, but it's Data Access Layer/Business Layer is too simplistic for an Enterprise Grade Application, and I would agree with you completely if you thought that, which is why I am writing this in the first place.
DotNetNuke is great at hosting an application, great at handling and managing user & role data, security and exception logging, content management functionality, and more, but it's data access ...
The following is copied from the original post in the DotNetNuke Forums:I could (and will and do) go on and on about the merits of using DotNetNuke as the base web application framework for Enterprise Development. I have developed several 'Enterprise' class modules, including a pharmaceutical prepackaging and labeling system for one client, a commercial shopping cart module sold on Snowcovered.com, a series of student registration, enrollment, and management modules for Polk County Public Schools in central Florida, and several free modules I host on my web site including a remix of the WROX Press book Building an ASP.NET Intranet document management system module for DNN 2 & 3 (source code free for download). All told, I probably have somewhere on the order of 4000-5000 hours of ... Read More »