I won't swear to having all of the answers but I'll attempt to answer what I
can!
______________________________________________________
Bill Grover
Supervisor IS Department Phone: 301.424.3300 x396
EU Services, Inc. FAX: 301.424.3300 x1396#
649 North Horners Lane E-Mail: mailto:[EMAIL PROTECTED]
Rockville, MD 20850-1299 WWW: www.euservices.com
______________________________________________________
> -----Original Message-----
>
> Date: Thu, 27 Apr 2000 10:14:14 -0400
> From: Jeff Shepler <[EMAIL PROTECTED]>
> To: "Cf-Talk (E-mail)" <[EMAIL PROTECTED]>
> Subject: Studio and Source Control
> Message-ID: <0DA2368A31D0D311A59900B0D0210674016F3211@MAIL-AK>
>
> Ok, I need some help with this - I'm missing something..
>
> Our CIO decided to implement source control for our web
> pages, so we ordered
> MS Visual SourceSafe. VSS comes with a very informative
> manual (none). Using
> an article from Allaire (
> http://www.allaire.com/Handlers/index.cfm?ID=12588&Method=Full ), I
> installed VSS on the web server, created a directory to be used as the
> working folder, created a project in VSS, added all the files
> from the web
> site, and set the working folder to what I created for it.
> Went over to my
> laptop, went into CFADMIN and filled out the SourceControl
> fields, created a
> local working directory, installed VSS (NetSetup from
> server), fired up
> CFStudio, created a new project, pointed it to the working
> directory, chose
> a source control, mapped it, launched it from Studio, told it
> to get current
> version of all the files in the project from the server, went back to
> Studio, and added all the files to the project.
>
> *whew*
>
> File Locations:
>
> Web pages: <webroot>\intranet\
> VSS working folder on server: d:\VSS Work Files\Intranet\
> VSS working folder on laptop: d:\CFProjects\Intranet\
> CFStudio project: d:\CFProjects\Intranet
> CFADMIN:
> Path to SrcSafe.ini: d:\Microsoft Visual Studio\VSS\
> Working Directory: d:\VSS Work Files\
>
> Yes, I work with the live files. Yes, I know it's a no-no. As
> soon I get
> this figured out, I'm going to make a copy of the intranet's
> folder and
> setup another web site for my development. Then I get to try
> and figure out
> how to automatically copy over changes (suggestions??).....
>
> But, first things first:
>
> Ok, the problem. I open up a file (checkout), make a change,
> save it, check
> it back in, the change isn't "live". Why not? Where is
> version 2 stored? It
> was my understanding that the working folders were only a place to
> temporarily put files being worked on. So, wouldn't that mean
> when the file
> was done being worked on that it would propagate to the
> original location
> (in this case, where the web pages are kept)??
Ok, let me ask this, where in source safe did you set where the file's
"live" location is. Answer: no place because there is no place to set it.
In source safe when you check out a file it places the latest version of the
file in the working folder of the person checking the file out, i.e. each
person/computer can have their own working folder. Once you finish the edit
and check the file back in you are simply updating the version in source
safe to know about the changes you just made to the file. To "push" the
file to your web site destination you will need to copy the file there
yourself.
When you check in the file it will leave the file behind in your working
folder, unless you told SourceSafe to remove the file.
You will notice that I said each person/computer can have their own working
folder. What I mean is that if you login to multiple computers each
computer can have a different working folder location and SourceSafe will
remember this.
>
> Do I need to set up some kind of deployment thing? If so,
> what do I need to
> do? I'm really rather lost here since I don't know where the
> files (version
> 2 from above) is actually kept (to copy it up to the live site).
You should have the latest copy in your working folder that you can copy.
>
> What is the use of telling CFADMIN about VSS? The notes say
> to make sure
> that the RDS service has sufficient rights to the working
> folder, but Studio
> isn't using RDS - it's local. Which then leads me to ask how
> do I set up a
> project to use RDS that will go through the server's VSS?
Probably because many people setup their working folders on a CF server.
What we do here is to have 2 CF servers. Our live server is running the
"released" version. We have a development server as well. We map our
working folders to a folder on this development server (usually
\\devserver\webdrive\inetpub\wwwroot\webworkfolder). Then when we check
files in and out the are placed into this folder. Since this folder is on
the CF server we can also use CF/IE/Netscape and test the pages while they
are being developed. Once the pages are tested and ready for release we
copy them to our live server.
BTW, you can do this on the same server with different web folders if you
wish.
>
> I'm basically having a hard time understanding how all of
> this fits and
> works together. I thought I did, but apparently, I don't. If
> some kind soul
> could take some time and detail out what I'm dealing with
> here (concepts,
> tips, suggestions) I would GREATLY appreciate it.
You can use CFStudio to push the files to the live server. If you use a
project there is a button for copying the project's files. When you click
this button CFStudio will prompt you for the destination to push the files
to. Once supplied CFStudio will go through every file in the project and
see if it is newer than the version in the destination. If so then it will
copy the file there. We use this feature to push changes to our website
once we are finished.
I'm sure I haven't answered all of your questions, and probably raised some
more. Feel free to drop me a line and I'll try to answer some more.
>
> -Jeff
>
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
