Say you have a main website running called
www.mywebsite.com and within IIS it would be located under Websites and it would have a default AppPool and run under a specific version of .NET framework. Say the website above holding all the code is located on your hard drive here C:\WebSites\MyWebsite.
This is setup within ISS, its a pointer for IIS to look find code to display the client. In this example lets say
www.mywebsite.com is running under .NET 2.0 framework with Managed Pipeline set to Classic. Also say this website has a few directories in it,
www.mywebsite.com/Admin
www.mywebsite.com/Memberswww.mywebsite.com/Documents. All of those folders exist in the main website directory located in C:\WebSites\MyWebSite. You'd have C:\WebSites\MyWebSite\Admin, C:\WebSites\MyWebSite\Members,
C:\WebSites\MyWebSite\Documents
Under that website you can add vitural directories. Lets call this one www.mywebsite.com/example that can have different AppPools, different sets of code, permissions, .NET framework, etc. These vitural directories
may or may not have access to interact with the main website or other vitural directory websites. The physical location on your hard drive is C:\Users\User1\Documents\Website\MyWebsite. Within IIS you give it the vitural name "example" and point it at the
location here C:\Users\User1\Documents\Website\MyWebsite and it will run the code in that directory. This particular website runs on .NET 4.0 framework and the Managed Pipeline is Integrated.
Again, they are different sets of code and may or may not intereact with each other.
Remember to mark as answer if this post answered or solved your problem.
b471code3
Star
13877 Points
2598 Posts
Re: Run a site from VS in the background with the command line
Jan 13, 2012 08:40 PM|LINK
Say you have a main website running called www.mywebsite.com and within IIS it would be located under Websites and it would have a default AppPool and run under a specific version of .NET framework. Say the website above holding all the code is located on your hard drive here C:\WebSites\MyWebsite. This is setup within ISS, its a pointer for IIS to look find code to display the client. In this example lets say www.mywebsite.com is running under .NET 2.0 framework with Managed Pipeline set to Classic. Also say this website has a few directories in it, www.mywebsite.com/Admin www.mywebsite.com/Members www.mywebsite.com/Documents. All of those folders exist in the main website directory located in C:\WebSites\MyWebSite. You'd have C:\WebSites\MyWebSite\Admin, C:\WebSites\MyWebSite\Members, C:\WebSites\MyWebSite\Documents
Under that website you can add vitural directories. Lets call this one www.mywebsite.com/example that can have different AppPools, different sets of code, permissions, .NET framework, etc. These vitural directories may or may not have access to interact with the main website or other vitural directory websites. The physical location on your hard drive is C:\Users\User1\Documents\Website\MyWebsite. Within IIS you give it the vitural name "example" and point it at the location here C:\Users\User1\Documents\Website\MyWebsite and it will run the code in that directory. This particular website runs on .NET 4.0 framework and the Managed Pipeline is Integrated.
Again, they are different sets of code and may or may not intereact with each other.