The (short) Problem We need to run the same website code, with a different web.config, on the same server.
The (Slightly longer) Problem The site needs to be hosted on 2 different domains, both on SSL, therefore, we need to have 2 different websites, on different IPs. However, we would like the codebase to be consistent for both of them, so when 1 get's updated, the other one is done at the same time. We also need to make each website use it different web.config (as there are values that are specific to each of the sites.
So, what we want really, is some way to define the location of the web.config for a .NET 4.0 aspx site from within the IIS configuration.
It's IIS 6.0 at the moment, but if IIS 7.0/7.5 will solve the issue then an upgrade is potentially an option.
Things I've thought of: Using symbolic links for all the folders and files other than the config. I'm not sure this is the best option as other files/directories could be added at some point and would be forgotten at deployment time. Synchronising the folders. This would mean that we're relying on a process to keep them upto date, either in real time or on a schedule. it's also a lot of overhead.