IIS Application Pools and ASP.Net 2.0

Application Pool Organization

Microsoft IIS 6.0 uses Application Pools to run web applications. Each application pool runs in its own worker process. This will allow you to configure each application pool to its own secuirity and resource consumption.

However, application pools cannot have both an ASP.Net 1.x and an ASP.Net 2.0 application running in the same pool. You can create a new application pool for the 2.0 apps.

The two extremes for application pools seem to be this:

1. Run everything in one application pool
2. Run each app in its own application pool

There are pro's and con's for each approach. I am asking readers:

1. What motivates you to put an application in one pool versus another?
2. When do you create a new application pool?