>>I don't think it can be done that way.
>>I believe it's possible to put all the web sites into one application and use URL re-writes to map different domain names to the relevant place. But I'm not sure why you would want to do that - bear in mind that HttpApplication only processes one request at a time and if you only have one instance it will presumably be taking a much larger loading.
>
>By "put all the Web sites into one application" seems to be what I have now. I have one directory serving various domains. However, because I have to create one IIS Web site for each site, this then creates an application for each of them, even if they all point to the same directory.
>
>Because, the way I have it now, this creates additional memory for each new site I create. Having them all into one application would then allow me to only use one memory location and would avoid loading a new application on the first hit of each of those Web site.

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