Contents tagged with Configuration
-
Workaround: Running ASP.NET 1.1 on Vista SP2/WS08 SP2
Many of you have probably read the article on how to install ASP.NET 1.1 on IIS7 on Vista and WS08 (The article can be found at http://learn.iis.net/page.aspx/472/how-to-install-aspnet-11-with-iis7-on-vista-and-windows-2008/).
-
Shared configuration and password expiration.
Most of you have probably heard of shared configuration. It is a simple and convenient way to centralize IIS configuration among multiple IIS instances. (More info on shared configuration can be found here.)
-
Setting up Shared configuration on IIS 7.0
Problem: When IIS 7.0 server is configured to work in shared configuration mode then configuration files are stored on a file share. This configuration is recommended for setting up web farms. But in case file share goes offline, the whole set up fails and web servers stop responding. Moreover when the file share comes up again, IIS server is not able to detect it gives following error message:
-
ApplicationHost.config file getting corrupted when OneCare or Forefront is running?
We have seen some reported cases when applicationHost.config file is getting corrupted when OneCare or Forefront is running on the same machine. By "corruption" I mean the XML is malformed is you may get an error:
-
Section level encryption of ASP.NET settings in IIS 7
As you know, ASP.NET supports section level encryption for protecting its configuration. It supports both RSA, which is default, and DPAPI out of the box and it also provides a way to use a custom protection provider. (Click here for more information on using RSA. Click here for DPAPI.) The most commonly encrypted sections are appSettings, connectionStrings, identity and sesstionState.