I have tackled this problem through using psexec (sysinternals.com)
executing remote commands to go through the steps of putting the
application into maintenance mode, removing the old files, laying the
new files down, warming up the site, then bringing the site back online.
It could be on in nant
Sent: Friday, November 04, 2005 10:01 AM
To: nant-users@lists.sourceforge.net
Subject: RE: [Nant-users] deploying asp.net applications
Thanks Ryan, this plan did cross my mind. The problem I have with it is how
to archive the old version remotely. Solving that problem, this might be a
good
Thanks Ryan, this plan did cross my mind. The problem I have with it is how
to archive the old version remotely. Solving that problem, this might be a
good solution.
-scott
From: "Ryan Davis" <[EMAIL PROTECTED]>
To: "'Scott Clemmons'"
<[EMAIL
Not necessarily common, but one way just popped into my head:
Store your application in a new directory every time you publish a new version,
and then change the IIS entry to have that web app
point to the new directory.
The process would become:
1. Build the new version
2. Zip the new version
