Published 2010-01-08 12:10
in The projects
Some IIS7 thoughts
As I wrote earlier I'm adding IIS 7 integration to Phantom and there are a lot of settings you can do in IIS 7. Most of them can be done in the web.config, and there is where you should do them. But there is one setting I've found to be important and that is the Application Pool. It is a good practice that each site has its own application pool. This leads to some design decisions that need to be done.
- When you create a site the systems tries to find a application pool with the same name. If it doesn't exists it creates a new application pool with that name.
- When creating a new site a parameter will be added so that you can specify the application pool name for that site. If you don't it will default to the same name as the site.
- When deleting a site there will be three options. Don't delete application pool, delete application pool if this instance has created it, force an application pool delete.
- The default delete option will be the middle one. Delete application pool if this instance has created it.
Thoughts and comments are appreciated.