We have somewhat of a disagreement going on around the shop here.
We have a huge web application that pretty much runs the entire operation. For some reason this app has been split up into multiple applications running in the same apppool. (See screenshot). Some in the shop claim that this setup is better because each app is protected from the other app so that if one goes down it wont eat up the resources for the other apps. I believe this is incorrect because all of the apps are running in a single app pool and the app pool is where memory and processor cycles are handled. This set up is also supposed to allow us to deploy individual parts of the app without taking down the entire site while the build runs. Basically each of the top level folders in our app has a cooresponding application in IIS in the default app pool. I don't see why we need to have a 1:1 relationship of deployment projects to app pools. IMO this setup causes a number of problems in Visual Studio with the web.config file, as in its near impossible to get web.config inheritcance to work properly when testing and error handling. We have a custom error handler that now has to be applied to each app since the applicaton context is the higest level of error handling available in ASP.NET.
Bascially I am wanting to know if we should be using one app pool with a single app and if the way the app is currently running even makes sense.
Let me know if I can provide clarification. It is a bit difficult to explain and to answer your next question...No, I didn't set it up this way. apppool.GIF