Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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...DNN best practice for upgrading to new version in the futureDNN best practice for upgrading to new version in the future
Previous
 
Next
New Post
7/22/2009 10:09 PM
 
airmanx86

Joined: 12/7/2008
Posts: 6
Hi,

I am new to DNN. I am hoping to learn the best practice when using DNN framework especially on the what not to do to allow easy upgrading to newer version of DNN in the future.

Obviously, I should not change the core DNN library, but how about the website which provided in the installation package? What are the components within the website that I should not touch at all?

Thank you in advance. Hoping to get some feedback soon :) Cheers!
 
New Post
7/26/2009 8:48 PM
 
airmanx86

Joined: 12/7/2008
Posts: 6

Is it safe to say that anything that could exist in an upgrade package should not be changed? i.e. both the core library and the website?
 
New Post
7/26/2009 9:41 PM
 
Johan Johansson


Joined: 12/15/2004
Posts: 407

Stay with standard component or with a very large 3:rd part supplier then the upgrade process will be much easier in the future .... and I recommend to put your site at PowerDNN because these guys will help you out with exactly that ...upgrades

/Johan Vattenskoter uthyrning

Kontorshotell Stockholm Skyltar  Rekryteringsföretag IT Support
 
New Post
7/27/2009 7:51 PM
 
Sebastian Leupold


Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

www.dnnwerk.de
Joined: 3/8/2004
Posts: 46212

As far as possible, you should stand away from modifying the core (library AND website) and packaged extensions  (i.e. modules, providers, skins and containers).

If you need to modify the core, you should carefully document your changes to be able to reapply it after an upgrade.

Instead of modifying core components, it is advisable to copy it and alter namespaces, to get modified custom versions, which will not be affected by upgrades.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/27/2009 11:29 PM
 
airmanx86

Joined: 12/7/2008
Posts: 6

Thanks Johan. I believe by standard component you mean both the core library and website. My project cannot be hosted by 3rd party provider, it must be hosted in house, but thanks for your recommendation.
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DNN best practice for upgrading to new version in the futureDNN best practice for upgrading to new version in the future


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