Now, not every site or application needs its own Application Pool, you can have some apps share a pool. ![]() On those systems, you just navigate to the site or application within IIS, go to ASP.NET tab and chose from the drop down menu the version that you want to run under. Where it starts to get tricky is when these apps need to run under different versions of. If there is a problem with /ImportantApp/ it will not affect the entire site, which continues to run nice and smooth. to its own pool.Įxample Configuration:hxxp://Site1 - runs under the Application Pool of "Site1_AppPool" hxxp://Site1/ImportantApp/ - runs under the Application Pool of "ImportantApp_AppPool" Goes bad, has a memory leak, or any other fault it is contained. These Application Pools spawn their own w3wp.exe worker process so if one application IIS 6 and higher is great in the fact that it allows multiple Application Pools to run on the server at once. One thing to remember is that multiple versions of ASP.NET can run within the same website, it’s just that each application needs to beĬontained within its own Application Pool. Running multiple versions of ASP.NET on one web server is not always easy and can get downright confusing.
0 Comments
Leave a Reply. |