7

I need to keep the production app settings section outside of Web.config; I don't want keys and other secret information to be kept inside source code repository. However, if I edit the app settings with IIS Mananger it changes the Web.config, which will be overwritten at the next deployment.

How can I keep those settings outside of the Web.config that comes with the application on deployment? For example, this is somehow done by Azure Web Sites - the app settings you configure in the portal are not stored in Web.config - that can be confirmed by downloading the file via FTP. How is it done?

5

For the appSettings and connectionStrings nodes in web.config you can move these into separate files outside of web.config.

In your web.config you would have:

<appSettings configSource="appsettings.config"></appSettings>

and then a new file appsettings.config:

 <?xml version="1.0"?>
 <appSettings>
     <add key="foo" value="bar" /> 
 </appSettings>

Then you have to make sure that you don't deploy these new files and keep them different on the production server and your dev environment.

All my web.config files are excluded from my deployment process, if I need to change them, I do that on the stage or production sites.

0

In addition to the web.config file(s) in your sites there are several global settings for IIS.

%systemroot%\System32\inetsrv\config\applicationHost.config

has all the global IIS settings, depending on your Feature Delegation settings these can be overwritten in your local web.config(s). But you can prevent this by setting a feature to 'Read Only' in Feature Delegation on the server level.

For dot.NET related settings there are two global files:

%systemroot%\Microsoft.NET\Framework??\v?.?.????\CONFIG\machine.config
%systemroot%\Microsoft.NET\Framework??\v?.?.????\CONFIG\web.config

There are several versions of these files, one for each framework version for each OS platform.

Any settings done in these files are inherited by your local web.config.

However I don't think there is a way that you can prevent a local web.config from overriding settings set in the global files.

  • 1
    Those will be global across all sites in IIS. What I need is a way to store per-site settings without having them overwritten when redeploying. – Mircea Chirea Feb 8 '14 at 18:40

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.