Comparing Visual SourceSafe and Vault



The other day, a reader emailed me  class=012433219-09062003>some questions regarding the functional
differences between Microsoft Visual
SourceSafe
 and href="http://www.sourcegear.com/vault/">SourceGear Vault. I’d rather
talk about the awesome sailing I enjoyed this weekend on a friend’s boat in the
lovely San Juan Islands class=012433219-09062003> but the
corporate Sirens are singing and I am now back on the clock.


Vault is a new source
control application from SourceGear, the company that produces href="http://www.sourcegear.com/sos">SourceOffsite, the most popular remote
access solution for Visual SourceSafe databases.


style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; mso-fareast-language: JA; mso-bidi-language: AR-SA">Question:
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; mso-fareast-language: JA; mso-bidi-language: AR-SA">Do
you know of some major differences between vault and sourceSafe that would lean
me towards using VSS?
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; mso-fareast-language: JA; mso-bidi-language: AR-SA">

Answer: I have not had an opportunity to evaluate
Vault personally.  However, I have seen it discussed in the following
newsgroups and listservs: href="http://msdn.microsoft.com/newsgroups/default.asp?url=/newsgroups/loadframes.asp?icp=msdn&slcid=us&newsgroup=microsoft.public.vstudio.sourcesafe">microsoft.public.vstudio.sourcesafe,
href="http://msdn.microsoft.com/newsgroups/default.asp?url=/newsgroups/loadframes.asp?icp=msdn&slcid=us&newsgroup=microsoft.public.vsnet.vss">microsoft.public.vsnet.vss,  class=012433219-09062003>and aspalliance.com’s href="mailto:product-vsnet@aspadvice.com">product-vsnet@aspadvice.com. class=012433219-09062003> class=012433219-09062003>


style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; mso-fareast-language: JA; mso-bidi-language: AR-SA">Question:
I work remotely and
access to source safe code depositories via VSS are excrutiatingly slow.  I
tried SourceOffSite and the access time was much better.  Will the VSS
improve responsiveness when accessing files remotely?


Answer: You can probably improve your performance somewhat by
tweaking a few VSS settings. For details, see  href="http://support.microsoft.com/support/kb/articles/Q123/4/73.asp">http://support.microsoft.com:80/support/kb/articles/Q123/4/73.asp (don’t
skip the last paragraph…from what I understand, shadowing can
be especially expensive.) Second, href="http://www.sourcegear.com/sos">SourceOffsite is often recommended as a
good third party solution for this situation. Finally, I often work remotely and
have observed that the fastest method by far is to connect to my
VSS client workstation on the corporate LAN via Remote Desktop
Connection (Start->Run->MSTSC) in Windows over a VPN. When connecting
via MSTSC, all of the heavy SourceSafe network traffic occurs on
the high speed LAN with only the screens being passed to me over my
[relatively] slow home connection.


style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; mso-fareast-language: JA; mso-bidi-language: AR-SA">Question:
What is the
history of VSS?  Was it developed at MS or did MS buy the product from
another vendor?

Answer:
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; mso-fareast-language: JA; mso-bidi-language: AR-SA">SourceSafe
was acquired by Microsoft in 1994 from OneTree Software. href="http://radio.weblogs.com/0117767/rss.xml">Ted Roche discusses the
history of SourceSafe in his book, “ href="http://www.hentzenwerke.com/catalogpricelists/essvss.htm">Essential
SourceSafe.”

style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; mso-fareast-language: JA; mso-bidi-language: AR-SA">
This posting is provided “AS IS” with
no warranties, and confers no rights.
size=2>Microsoft kann für die Richtigkeit und Vollständigkeit der Inhalte in
dieser Newsgroup keine Haftung übernehmen.
size=2>Este mensaje se proporciona “como está” sin garantías de ninguna clase, y
no otorga ningún derecho.