Angel02
asked on
Hosting multiple websites on IIS: website vs Application vs Virtual directory
I need to host two different asp.net web applications on a new web server. Previously, they were hosted on IIS 6 and were added as a virtual directory each under the Default Website.
Now I am in IIS 7 and need to host those two web applications. If I right-click Default Website and add the two web applications as new Virtual directory or new Application, I can access them as
http://MyWebServer/WebApp1
http://MyWebServer/WebApp2
Which is OK and easy.
But if I right click on "Sites" -> Add Website to add the two applications as Websites, do I have to give them two different hostnames to distinguish? I would like to access the two applications like above mentioned links so the end-users are not confused. I am not sure how their URL's will be if I add them as WebSites.
Can you please give me the advantages of adding as WebSites over Virtual Directory or Application?
If it does not effect performance or speed, I would like to add the web applications as Virtual Directory or Applications. Please advise.
Now I am in IIS 7 and need to host those two web applications. If I right-click Default Website and add the two web applications as new Virtual directory or new Application, I can access them as
http://MyWebServer/WebApp1
http://MyWebServer/WebApp2
Which is OK and easy.
But if I right click on "Sites" -> Add Website to add the two applications as Websites, do I have to give them two different hostnames to distinguish? I would like to access the two applications like above mentioned links so the end-users are not confused. I am not sure how their URL's will be if I add them as WebSites.
Can you please give me the advantages of adding as WebSites over Virtual Directory or Application?
If it does not effect performance or speed, I would like to add the web applications as Virtual Directory or Applications. Please advise.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Virtual Directories.
ASKER
If I add as Virtual Directories, they will use the application pool, asp.net version and default document assigned to the default website, correct?
If the default document is different for both my web applications, should I add them as Applciations instead of Virtual directories? Are there any advantages of adding as virtual directory?
If the default document is different for both my web applications, should I add them as Applciations instead of Virtual directories? Are there any advantages of adding as virtual directory?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
If there are no objective to worry about (like http://mywebserver/WebApp1;http://mywebserver/WebApp2), is there an advantage of adding as websites over adding as virtual directories?
As individual web sites, they can be accessed by their own DNS names (www.website1.com, www.website2.com) versus being accessed at a common URL (www.website.com/VD1, www.website.com/VD2).
ASKER