In VSS set the "Working folder" to be the dev server. If you're working in a shared dev environment you'll need to ensure that people only edit files they have checked out, since the act of "checking out" changes the file from read-only to writeable. How this is handled depends on the editor. If you have developers working locally then you'll need to ensure your local copy of the codebase matches the VSS one. A regular "get latest version" in VSS should do the trick, along with good communication to ensure you don't have multiple developers doing conflicting things locally.
Getting from VSS to test can be a bit more of a shag, depending on your situation. One thing i've found that helps is to create a second VSS user, and for this user you set the working folder to point to the test server. When releasing stuff to tets you log in as this second user. This allows you to compare VSS to the test codesbase, and use "get latest version" to get the code to test. For minor realeases, with a large code base, and regular updates and multiple developers, i will build the next release by taking a copy of the current one, comparing it to the latest version in VSS, and doing "get latest" on individual templates. For major release we'll develop up to a point, then get to a point where everything checked into VSS is destined for the release. Then i'll do a "get latest version" on the whole lot, and move that up to test. During the testing cycle fixes are applied to the test base in the same way as minor release, ie using VSS to compare contents and get latest on individual templates. Once the test code base has passed all the tests it is then FTPed up to live, and when the time is right it is switched on. This works well, but moving the entire codebase might not suit evereyone, but we do regular releases (about one a month) to 2 servers running a total of 7 sites on the same codebase, serving over 4 million pages/week. The ability to throw a switch to the new version (and back when things go t*ts up) is invaluable. The way i do this is summed up below. "myapp" is a cf mapping, under which are a bunch of folders, named after the release, and containing the codebase for that release. application.cfm: <cfset currentversion = "2.3.3"> index.cfm <cfinclude template="/myapp/#currentversion#/index.cfm"> I've probably strayed from the question, but HTH anyway. Cheers Bert On Tue, 11 Jan 2005 11:06:04 +0000, John Beynon <[EMAIL PROTECTED]> wrote: > Hi there, > I'm trying to get my head round a decent sourcesafe environment setup. > I have developers using DWMX who will (i guess) have a local folder > setup for checking out files from the repository for editing - that > bit i'm ok with. > > How do folk get stuff from SS onto a DEV server? I'm thinking i would > have to checkout the entire project from sourcesafe to a local folder > and then FTP it up to a DEV server and use a similar techique for > getting stuff onto the LIVE server from the repo... > > how do others handle it? > > thanks, > > jb. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:189898 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
