title: Best way to deploy website - App pool start stop or website start stop
body: <p>What is the best way to deploy changes to a website( replace the dlls and other required files) ?</p>
  
  <p>Should the website be stopped and started or should the app pool be stopped and started?</p>
  
  <p>I read that when a website is stopped, it still has the application state loaded in memory. In this case will the old request be served ? Can the dlls be replaced without any problem ? How does the content gets reloaded when the website is started?</p>
  
  <p>When the app pool is stopped, will it continue to serve the old requests? If yes, how does the old request gets served considering the website is now containing the changed dlls?</p>