Rolling out entire site, or only changed pages/elements? (ASP.NET)

We use ASP.NET, C#

When making an update to one of our websites, we roll out the entire site rather than updating just the pages or sections that have changed. This scares me.

Is this a good idea? Should I roll out only the changes?

Should I break my site into smaller projects?

What is best practice?

From stackoverflow Jason

• You should always roll out the entire site. Because the actually executable code is contained mostly in the DLLs, you can't actually only roll out the pages that changed, like you could with the old ASP. If there are parts of your website that are actually separate, you can break them apart into separate projects, and deploy each entire section separately.

  Also, if putting up the whole site scares you, you probably need better testing or quality assurance standards. There should always be a copy of your entire site that can go live at any time, in case the server dies, and you have to replace it, or something else goes wrong.

  From Kibbee

• Depends on how you test prior to deployment.

  If you (automatically) test everything prior to release, isn't the only downside the overhead of the file transfer.

  Jason : I don't test everything... I only test my changes and what it affects.
  From Matt Lacey

• A full dump is best if the project is tested as a whole; However, individual pages are generally acceptable when your changes are individually regression tested. Just make sure your assembly references are properly versioned :)

  From tsilb