>Using the same directory is not relevant. You don't have to create a separate IIS web site for each domain. The idea is to route them all to the same site then use url rewrites to map them to the relevant folders in that site. There are several options for handling the re-write. Here's an overview:http://msdn.microsoft.com/en-us/library/ms972974.aspx

Well, if I can do that, then, this would avoid me to create a Web site for each of those sites. The only reason I created one was to have IIS to respond to the domain. However, there was a setting that I was applying to each of them, on an occasional basis, and it was to remove the anynomous access. But, I can do that at the application level.

This would then resolve the issue of having only one application loaded in memory, thus I would save some memory space here, and the first hit on each of those Web sites would then create the application initialization. Then, the first hit on additional domain would then avoid creating that again. This would then make my application object visible across all domains, no matter on which site I sit on.

I will take a look at that link and will let you know about my research.