Home/ Questions/Q 1077013
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T21:30:44+00:00

I want to be able to quickly deploy updates to a site that is

  • 0

I want to be able to quickly deploy updates to a site that is fairly busy. For smaller sites I would just FTP the new files over the old ones. This one, however, has a few large dll’s that regularly get updated and while they are copying the site is effectively down (plus there is the hassle of making backups of them in case something goes wrong.

My plan is to use TortoiseHg to synchronise with a staging copy on the server over FTP (using netdrive or something similar). I can then check all is running smoothly and once that is complete I would like to run a .bat file (or something else) that will create a backup of the live site (preferably only the files that are about to change, but that is not critical) and then copy the newly changed files over to the live site.

If possible I also want to have the copy ignore certain directories (like user uploads) so that it won’t overwrite those files on the live site?

I’ve heard RoboCopy is the way to go but I’m not sure of where to start. Would I need to call 2 commands (1 for the initial backup and one for the copy)? Is there any way to restore the live site to it’s previous state should something go wrong?

The site is in ASP.NET and would be copied to Windows 2003 server.

EDIT: It gets a little tricky when web.config items have changed and need to be merged so that the staging servers settings (appsettings, connection strings, etc) don’t get deployed to the live site. How does that get handled?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    What we use is the following

    • first build the website with msbuild in cruisecontrol.net to build the binaries

    • archive the currently deployed files under a timestamped folder to avoid losing data in case of a problem

      C:\DevTools\Robocopy\robocopy.exe /R:1 /W:10 /mir "D:\WebSite\Files" "D:\Webarchive\ArchivedFiles\Documents.%date:~0,-8%.%date:~3,-5%.%date:~6%.%time:~0,-9%.%time:~3,-6%.%time:~6,-3%" /XF *.scc

    • stop the website

    • deploy the website by copying everything except the files we archived (/XD is eXclude Directory)

      C:\DevTools\Robocopy\robocopy.exe /R:1 /W:10 /mir "c:\dev\site" "D:\WebSite" /XF *.scc /XD "D:\WebSite\Files"

    • copy and rename (with xcopy, this time) a release.config with correct information to d:\Website\web.config (in fact, that’s what we used to do, now we have a homebrew transformation engine to change parts of the dev web.config on the fly).

    • restart the website
    • (optional) delete the archive you made at step two

    In your case, you’ll have to add the /XD flags for any directory you want to ignore, such as the users’ upload. And unless the production web.config file is complicated, i’d really recommend simply copying a release.config that you maintain as a part of the project, side by side with the web.config

    • 0