An additional problem is that Web.config files were designed to be changed at any time, even after the Web-based applications are in production.

A major area where security is often lax is the web.config file. Usually stored in plain text, an intruder who gains access to this file can then easily access databases and other resources both ...

Tweaking the settings in your configuration files in ASP.Net can provide a nice performance boost. These files include machine.config and web.config. The web.config file is application-specific ...

The ability for Visual Studio to automatically transform your development Web.config file into a production version is certainly convenient ... but only if the transformation is done right. Here's how ...

Likewise, the Machine.config system file provides ASP.NET configuration settings for the entire Web server and forms the base settings for Web.config files used within an ASP.NET application ...

According to Microsoft developer documentation about transformation syntax for Web.config -- the primary configuration file for any Web service -- a transform file is an XML file specifying how the ...

App.config and Web.config files are a great way to add flexibility to your .NET application without having to modify code in the future. They also allow clients or end users to make configuration ...

Can you put the various environment keys into their own .config file, and then include that file in the main web.config? Then you can just add in the correct .config in your build/install scripts.

The C# code when the look at the app.config during runtime to grab the proper datasouce. What I have found is that this is easy to do with an .EXE file but apparently a lot messier using a DLL ...