Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have situations where we have multiple virtual directories pointing to the same physical folder, and I am wondering if this could cause any issues or if it is a supported configuration in IIS.

For example, we install our software to folder c:\software\mywebservice

We setup a virtual directory for anonymous access pointing to this physical folder.

We setup a 2nd virtual directory for Integrated Security access pointing to the same physical folder.

Is this type of configuration OK, or are there any potential side effects that anyone knows about?

Kind Regards


share|improve this question
up vote 2 down vote accepted

It should be fine, the only thing to be careful is now that IIS 7 and above can use web.config files inside the content to store their settings (like directory browsing, and others) you could run into the problem that modifying a value for one will have the side-effect to change the other as well since both of them share the same web.config. One way to achieve that without affecting the other is to use paths inside ApplicationHost.config or the root web.config depending on if you are modifying settings of ASP.NET/WCF or IIS. But other than that you shouldn't have any problems.

share|improve this answer
I use a similar setup, and have several virtual directories pointing to the same physical directory. I have no issues with it, but as Carlos points out, changes to the settings for that virtual directory under one site/directory will most likely be written out to the web.config in that physical dir, and applied to all of them. – Jon Angliss Jul 6 '10 at 4:13

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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