Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Dotnetnuke as an enterprise development platform?Dotnetnuke as an enterprise development platform?
Previous
 
Next
New Post
9/2/2008 9:00 AM
 

We're considering the use of DNN as the basis of our customer-facing applications, which are currently developed in a conventional corporate environment - i.e. we have development, test and live servers, and each change is progressed from the development platform to the test platform before being deployed on the live server. Does anyone have any experience of implementing and maintaining a DNN environment in this way? If so, how easy is it to maintain separate development, test and live platforms, and to migrate new application releases from one platform to the other?

Are there any other considerations when thinking about DNN as an enterprise development platform?

 
New Post
9/2/2008 10:19 AM
 

I use to develop DNN inside a corporation and it was very smooth.   I had my local computer setup as a development enviroment.  I had a test server that customers would use to evaluate changes and then I had a live server which was available to all users.

With Dotnetnuke supporting Modules, it makes it a breeze to perform the project life-cycle on it.

I wouldn't hesitate to use it on an enterprise situation.

Stuart


Hilbert Solutions, LLC
Owner, Hilbert Solutions, LLC
http://www.HilbertSolutions.com
A DNN Service Provider
From Module Development to DNN Upgrades, your one stop DNN Shop
 
New Post
9/2/2008 10:46 AM
 

There are a lot of things to consider when running DNN as an enterprise solution, but as with any application the limitation will be developing and managing those strategies properly.

Development/Testing/Deployment of modules for your application will be key, if you have a good process defined though that management/deployment can be made very easy through the use of packaging scripts and even deployment of these new modules/packages can be automated


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
9/3/2008 9:02 AM
 

Thanks for the feedback. Since much of DotNetNuke's configuration is held in the same database as user data (e.g. business transactions, user details, etc), I was curious as to how easy it is to isolate configuration changes in test databases from user data, so that these changes can be migrated from test to live databases without impacting user data.

Is it easy to separate such metadata (e.g. page and module definitions) from user data? When releasing updates from test to live environments?

 
New Post
9/3/2008 11:07 AM
 

"Easy" depends on your command of SQL Server...  :)

In most cases a development environment would be built to match the deployed system, code developed and tested there, modules created and packaged and then the module uploaded on the production server.

Jeff

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Dotnetnuke as an enterprise development platform?Dotnetnuke as an enterprise development platform?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out