title: Reasons for C# projects to rebuild in Visual Studio
body: <p>I have a large solution, of some 320 projects, where even small changes to a single web form result in long build times to test/debug a small change.  I suspect post-build file copy tasks for 'touching' file datetimes and causing multiple rebuilds.</p>
  
  <p>Are there any other reasons for VS 2010 to run a rebuild other than source files being newer than binary output files, in the absence of any strong naming and versioning influences?</p>
  
  <p>ADDENDUM:  I have no immediate influence on the size or shape of the source tree.  It is the trunk of a stable core product and any short-term "non-business" changes are considered risky and or costly.  I will raise points mentioned in answers I receive here as input to future directions of the project.</p>