A local web.config file forbidding read access to it would be a nice solution. What should be the contents of a web.config file to forbid web access to the files?

3 It depends if your application reads the configuration file every time it needs the setting, or monitors the file for changes (like log4net does). If not, you need to restart the application. Note that by …

Without -commit:apphost, APPCMD will target the closest logical spot for a web.config file - whether at the site or app level, and indicate it's changed the setting using a configuration string like the above …

You do have to worry about users reading web.config files. Especially, if you are allowing users access to your file system. I've tried removing user permissions to the web.config and allowing only the …

0 Try removing your original web.config (create a backup first), and after making changes via IIS (it will create a new web.config), restore the original changes you'd made to the file.

in Web.config file and put all files not with in a subfolder so that user can type Url only instead of Url/subfolder.... Here clear is the main thing to be done which will clear all other default docs with in …

The ASP.NET AppDomain is restarted whenever you 'touch' web.config. It's possible to turn off the File Change Notification (FCN) for a folder, but it's usually not the best bet if you can help it.

Are you sure web.config is the best place to store what you're storing? You may want to consider moving your settings to a database. I bet with a config file that large that the starting up for your app …

Applicationhost.config contains entries applicable to either bitness32 or bitness64 using preConditions, so it's cross-bitness. Web.config files at lower levels in your site or content folders can also use …

Best guess: The application pool seems to be having difficulty reading a web.config file in the directory or one of its subfolders. NTFS permissions probably prevent it from doing so. The app pool starts up …