November Happy Hour will be moved to Thursday December 5th.
AI OnAI Off
Best practice for web.config handling in SCM.
Hi,
this is a very good question, and unfortunatly I have no good answers. If you google "appSettings file" you'll find many good discussions on best practices for handling this kind of problems, specifically for dev / test / production.
I've seen some suggestions on naming your web.config files like .web.config and using scripts to copy the correct file to the site. It needs to be automatic, or at least semi-automatic to avoid problems and confusion. The machine specific versions should be committed to source control, and all global changes should be applied to all files during development to keep the files in sync.
As you write, the
#15122
I also added a key to web.config and appsettings.config:
web.config:
From code I did some tests:
System.Web.Configuration.WebConfigurationManager.AppSettings["MySetting"]
--> "appsettings.config"
Global.EPConfig["MySetting"]
--> "web.config"
ConfigurationSettings.AppSettings["MySetting"]
--> "appsettings.config"
So, for your own code, you can use this feature, as long as you do not use the ApplicationConfiguration class in EPiServer (Global.EPConfig and PageBase.Configuration).
Unfortunatly, EPiServer uses its own reader to get the values from web.config (the web.config file is read and parsed as a ordinary xml file), which is why this does not work with the EPiServer settings. I know that the config system in EPiServer is getting an overhaul in 5.0, but I don't know if the file attribute on the appSettings element or the configSource attribute on all config sections will be supported. Hope so :-)
/Steve
Feb 16, 2007 15:14
