title: ASP.NET website deployment best practices resource suggestions
body: <p>I have looked through the related questions, and none of them have provided me the information I am looking for.</p>
  
  <p>Currently the team I work on does deployments of individual .aspx (and .aspx.vb) files for bug fixes/enhancments.  I am trying to affect change, as I really believe that deploying the "whole compiled site" is less error prone.  As this is a significant change from the way things have been done, my suggestions have ben met with significant resistance.</p>
  
  <p>As my google-fu has not been up to par lately, I was hoping the SO community could either tell me that I am off my rocker, and that there is nothing wrong with moving individual files, or point me to some really good resources which would allow me to make a stronger case.</p>
  
  <p><strong>Edit:</strong></p>
  
  <p>This has all been great info, and reinforces the arguments that I have already been making, can anyone argue the other side?</p>