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
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Changes that must be preserved in web.config on upgradeChanges that must be preserved in web.config on upgrade
Previous
 
Next
New Post
9/19/2008 11:02 AM
 
jberganz

Joined: 8/27/2007
Posts: 43

I noticed a line in the installation guide in the upgrade section that stated:

"Make any other changes to web.config that you made to support additional providers etc."

In general do you know where these changes might take place?  Are there any tags or sections in particular in the config file that are altered dynamically as different modules and providers are added to the dotnetnuke instance or are all the changes manually setup by users?  How exactly does the web.config file change as a dnn instance is extended? Any help or insight would be greatly appreciated.

Thanks in advance,

 

Jose 

 
New Post
9/19/2008 11:20 AM
 
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

usually changes are needed for providers, which require modifying the web.config file manually. Since DNN 4.6.2, modules may alter web.config as well, but the same time these versions will adjust the web.config file appropriately itself during install and unburden you from this task.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/1/2008 1:10 PM
 
jberganz

Joined: 8/27/2007
Posts: 43

Thanks for the info.  I am working with several dnn instances that are a lower version of 4.6.2.  Is it safe to say that any modules I have added did not affect the web.config file?  If a module generated change is copied over to the release.config file during an upgrade will the upgrade fail or pass?
 
New Post
10/1/2008 4:24 PM
 
Jeff Cochran


Joined: 6/3/2005
Posts: 2799

Compare the old and new web.config files (or web.config and release.config).  I like BeyondCompare for this, but WinDiff works too.

Jeff
 
New Post
10/1/2008 4:29 PM
 
Oscar Martin

www.bestwebsites.co.nz
Joined: 3/24/2004
Posts: 419

Yeah, using a file compare is a good idea.  But only old settings that relate to modules you have installed.  If a setting for a core module is different, it is likely that the new version is the correct one.

Of course you still need to copy connection strings and machine validation key.

JK

You know your website is cool, so why not let your users help you by spreading the word on social networking sites - get the DotNetNuke Social Bookmarks Module with 57 different ways to add social bookmarks to your site ... or download the FREE demo right now
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Changes that must be preserved in web.config on upgradeChanges that must be preserved in web.config on upgrade


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