SCC tools came out of client/server world ĬF Developers are often spread out geographically ĭesigned with teams of LAN-connected developers in mind Provide means to share repository on a LAN Team development challenges Problems solved by SCC Challenges to using it   Ĭultural Organizational/technical Remote developer access Today’s presentation is also offered on my site “Version Control and ColdFusion” Also offered associated paper with more details Focus was more on “Starbase” product offered free to CF users by Allaire, prior to CF 3.1 Still a useful talk/paper for basics of SCC and setup in Studio I presented a talk here at MD CFUG 3 years ago  You need to learn about SCC It’s great, powerful, and more than can be discussed today in detail. If not using SCC at all (whether with VSS or other)   There are other SCC programs (MKS, Starbase, PVCS, etc.) Solution offered here applies only to VSS Primarily VSS users, needing remote access to SCC repository (will explain)  How many are using some form of source code control? How many of those have problems allowing remote developers to access the SCC repository? How many have tried to get Allaire’s “Server Side Source Code Control” to work? How many using SCC are using Visual Source Safe? How many are using SourceOffSite? Why Source Code Control (SCC)? Challenge: remote developer access Allaire’s attempted solution Solving problem for Visual SourceSafe (VSS) users: SourceOffSite (SOS) Getting, Using SOS Challenges to the SOS Coming improvements to SOS

Server-Side Source Control It really can work! Charlie Arehart SysteManage

Allaire coldfusion studio