I have a client who wants to operate a Dot Net Nuke site as "managed code."

Normally this includes:

• Site development on a developmental system
• Testing on a second system
• Checking the tested site into configuration management
• Publishing to a live system from the managed code base

My impression, having used DNN now for a time, is that this is made more difficult by the DNN framework what provides tools to update code from within the DNN site.  Further, since "code" also includes work inside of the database, managing this SQL code is also difficult. 

Added to this is content management as much of a site's content resides in the database and can be managed quite easily in the context of the DNN site, but is not as easily managed in a configuration controlled environment.

So ... is this sort of notion whistling in the wind?  How to people manage ... and CONTROL ...their DNN sites?

---

Joe Craig
Patapsco Research Group, Ellicott City, MD
DotNetNuke Development and Services (http://patapscorg.com)