Wiki Home

Source OffSite


Namespace: B2B
A great way to share Visual Source Safe projects over the internet. http://www.sourceoffsite.com.

We use this constantly, and I think Source OffSite is the coolest new tool I've seen this year.-- Steven Black
We (Vision Data Solutions) have had 10+ developers using SOS for several projects for over a year. How did we ever survive without it? -- Kelly Conway
SOS is indeed pretty cool ... but I do wish it had some of the features that VSS does. Most notable are two: search (by status is the one I use often in VSS) and the ability to differentiate, during a Get Latest operation, between files which are writable but unchanged, vs those which are writable and changed. Either you have to overwrite all writable files or none of them.

The VSS implementation is cool because I turn off all ReadOnly attributes in my project directory (Super Class works better this way, and menus are editable too!) - Zahid Ali
Has anyone tried running SOS as the Active source control provider in VFP and integrated with a project? Is it just me or is this extra flaky integrated source control compared to VSS6? If I connect to the remote VSS project from the VFP6SP3 Project Manager it always creates a sub project of the same name and duplicates everything.

Worse yet, I cant get it to go away now... I've disconnected the project in VFP from source control, set Active Provider under Options to none, and tried to find something in the pjx table. But it still prompts me to connect to server every time I open the dang project. I'm extremely happy using the native SOS client IDE, so how can I make the project manager connection mess go away? -- Rox
According to SourceGear (the publisher of SOS), SOS is a worthwhile option, even if you have an Internet connection to your database that the native Visual Source Safe client can use. They give two reasons for this: the client-server architecture of SOS makes it faster than the client-based VSS client, and SOS does not commit changes until after transmission, limiting the likelihood of data corruption. I have not verified either of these claims. -- Zahid Ali
Awesome product that allows you to access all your Source Safe capabilities over a low bandwidth connection. It's so nice, we use it in the office as well as at home/clients. Very intuitive interface and adheres to the SCC API (Source Code Control API) so that it hooks right into the VStudio tools just like any source control program.

Two thumbs up.

-- YAlan Griver
See also Source Surf
Also: A review of Source OffSite Collaborative Edition: http://www.cornerstonenw.com/article_id_collab1.htm
The latest version of SOS is 4.0 and is now available. See http://sourcegear.com/sos/index.asp. A major change is the server component is now built with .NET instead of Java. The client piece is still written in MFC.
I'm evaluating SOS right now. I would like to use the PM integration but all that is visible in the options dropdown for SCC is Microsoft Visual Source Safe. We will still be using the normal VSS client on the LAN connections. I just need better WAN capabilities since I tend to work out of the office a lot. Any problems with using the 2 clients together? My laptop will stay SOS once I have it configured and working, just want to make sure other clients can still be regular VSS. -- Randy Jean

You should be fine, Randy. Just be aware that SOS has two different commands to refresh the project tree and the file list, and these refreshes often need to be triggered manually since SOS is optimized for reduced traffic over the wire. That said, I wouldn't dream of using VSS integration. I think that, overall, the SOS client is just a far superior client than anything the PM gives you. Translation: I use SOS all the time, even when on the LAN.-- Steven Black

I probably would use it everywhere, too, but I don't want to have to purchase all those seats unless other people here actually need to work off site (can't see that happening), but I definitely need to do this all the time. But, I also have a desktop I use at work and the laptop is pretty much ONLY for offsite use. So, if I clear out the PM stuff on my laptop and just use SOS client, should I also get rid of any vss, pjm, vca, fra, etc. files? I assume only PM integration uses these, otherwise SOS client just deals with the binary files, right? What about doing DIFF stuff on vcx, mnx, etc. In other words, I need to support a mixed environmetn of SOS, VSS, PM integration, etc. Thanks for your feedback Steven -- Randy Jean
Has anyone moved to Source Gear Vault from Source Safe ? I am running Source Safe and am looking at going to SOS but noticed that I can get the licences for Vault cheaper than I can for SOS. It's actually cheaper for me to move over to Vault. I'm comfortable with VSS and SOS seems great but Vault looks good also. Infact, this page suggests that Source Any Where is the best choice if you only work in Windows - http://www.bettervssremoting.com/ -- Jamie Osborn

Hi Jamie, yes we here at ProLib (15+ VFP programmers) have just switched from "traditional" VSS with SOS to VAULT. The import of the VSS databases went almost flawlessly; as long as VSS isn't reporting any errors on them, you shouldn't experience any problems. Two points for a sucessful import: Set up a clean machine with an ENGLISH (not localized) version of VSS 6.0C (not the latest one!), then copy the VSS files over to that machine (so that the importer can access them as local files), then start the importer and be prepared for some long time. Some of our projects took several hours to import.
After you imported everything, uninstall VSS completely from your development boxes and install the VAULT client. The communication to the server is based on Web Services, thus you can access your data from anywhere. They also provide a pure Web-Interface, whee you can retrieve (download) a file directly. I

Integration with VFP is almost as with VSS; but we are currently experiencing a minor problem: If you want to add a new project to VAULT directly from within VFP, you can't leave the "Select project node" dialog. Current solution is to create the new procject node interactively from the real Vault-client interface, and then just select that node from within VFP.

Besides of that, VAULT is notesibly faster than the SOS client, and has some added funtionality. ChrisW likes the "BLAME" option . For a local (or test) installation, you could use MSDE as repository. -- ?wOOdy

Choose Source Anywhere! Our company Morningstar, http://www.morningstar.com, has 280+ developers working on Dynamsoft Source Anywhere for VSS. We have 72G data. With one HP server, Source Anywhere for VSS can handle all the requests. We recently upgraded to 5.2. It is even better. The company recommended us take a look at Source Anywhere Standalone. They claim Source Anywhere Stanalone solves all the Source Safe issues.

Tim

Category Development Tools, Category Configuration Management, Category Source Code Control, Category Project Management, Category Tools
( Topic last updated: 2007.10.11 05:16:34 PM )