I was told that every time I refresh our web site, either individual pages or the entire site, I should first stop the application pool, update my website file or files, then start the application pool. My web site files consists, of HTML, JS, ASPX, INC, GIF, JPEG, CONFIG, etcetera. I'm asking because I believe I have updated my site without stopping the application pool and starting it, and also by stopping and starting it, just trying to find out what the correct approach should be.
When Should I Stop/Start an IIS Application Pool
application-poolsiis-7webwebsite
Related Topic
- Why is IIS6 using the web site anonymous user account for file access instead of the app pool account
- IIS 7.5 Application Pool stops on page request
- IIS 7.5 Doesn’t Load Static HTML Pages – Troubleshooting Guide
- PHP + IIS Application Pool Identity Windows\Temp permissions
- Win Server 2008 + IIS 7 + MVC3: what to install to deploy applications
- IIS 7.x Application Pool Best Practices
- What permission(s) does an application pool identity required to manage other application pools
Best Answer
You don't have to recycle or re-start your application pool when you update your site. Neither for adding/updating files nor for updating your web.config.
IIS picks up all changes automatically.
Reasons for why you may want to recycle include:
By default an application pool is recycled every 29 hours, so usually you'll never have to recycle an app pool manually.