title: Does Visual Studio Publish to Azure Website Cause Whole Site to Recycle?
body: <p>We've recently launched a new website in Azure (i.e. Azure Websites) and as is typical with new launches we've had to deploy a few tweaks to fix minor issues shortly after launch. </p>
  
  <p>We want to use Slots in the long run but this is not possible at the moment. Hence we are deploying to the live site. It's a fairly busy site with a good amount of traffic and obviously want to keep downtime to am minimum. </p>
  
  <p>We are using Visual Studio to publish file changes to Azure but have noticed that even if we publish a relatively insignificant single file the whole site goes down and struggles to come back up. I was assuming that publishing a single file would literally just replace that file on the file system but it's behaving more like it recycles the application pool (or Azure equivalent) for the site. The type of files I've been publishing have been Razor views, hence would not typically cause a recycle.</p>
  
  <p>Does anyone know what actually happens under the hood of VS Publish and if there is a way to avoid this happening?</p>
  
  <p>Thanks.</p>