Sounds fine to me, I do similar things.  The only caveat would be that I
would also get Source Safe to do all clever checks to see that you have all
the files in the version of Source Safe you want them in.   As here we have
had incidents where a new file has not been put under Source Safe control.
So now, any time we copy, we do all the "files here / files there"
comparison combinations just to be sure we haven't missed anything.

John

----- Original Message -----
From: "Peter Lanoie" <planoie@e...>
To: "Interdev_Programming" <interdev_programming@p...>
Sent: Wednesday, December 27, 2000 6:06 PM
Subject: Server to server web copying


> Hello Fellow Interdev-ites!
>
> I have a slightly complicated question I'm hoping someone can help me
with.
>
> Here is the situation:
> I have two web servers.  One is a development server (server1), the other
is
> a mirror of a production site (server2).
> Currently, BOTH server's primary web's are set up with source control
> (Visual Source Safe), and the source control database resides on the
> development server (server1).  This whole setup was something that I
> accomplished recently, since our last production release.  So I was able
to
> simply move the web over manually and tie it back in to the existing
source
> control.
>
> Here is the goal:
> Once our release (from the development server (server1) to the production
> server) is complete, I need to copy the entire web from the development
> machine (which is now a duplicate of production) to the production mirror
> machine (server2).  Normally, when we release to production, we simply
> transfer the effected files to the production machine's web folder from
the
> development machine.  The catch here is that we need to be able to also
> update the source control for the internal production mirror machine's web
> (on server2).
>
> Here's what I think I might be able to do, but would like some other
> opinions on it:
> 1. Check out the entire production mirror project (on server2)
> 2. Copy all the web files from the development project (server1) over the
> existing production mirror web on my local working directory (for Visual
> Interdev)
> 3. Check everything back in as the new release version.
>
> Does this make sense?  Am I overlooking something much simpler?  I haven't
> worked at all with Interdev/Server Extensions web deployment capabilities.
> Again, the main key is that I want to be able to copy the development web
> onto the production mirror web, and update that web's source control
project
> with the new release copies of the files.
>
> Thanks for any assistance.
>
> Peter Lanoie
>
>

---
http://www.asptoday.com - the leading site for timely,
in-depth information for ASP developers everywhere.
---
You are currently subscribed to interdev_programming as: $subst('Recip.EmailAddr')
To unsubscribe send a blank email to leave-interdev_programming-$subst('Recip.MemberIDChar')@p2p.wrox.com