Geeks With Blogs
Patrice Calve Life's short, have fun

I just finished setting up a Web Enabled Visual Source Safe 2005 Server.  It's a WebService, great, but...

What I don't understand, is that on the client side, you need to specify a Windows Share.  Isn't the WebService's whole idea is to go around this? 

I see 3 options:

  1. Use local db (for personal stuff)
  2. Use an UNC share (like what we're use to)
  3. Use a WebServer (for when a share isn't a good solution)

For option 3, it would be great for devs that work at remote locations and/or “sourceforge like” hosters.  ex: 2-3 friends that work on a small app.

Or consultants that work remotely for an organisation...


Posted on Monday, April 24, 2006 1:34 PM | Back to top

Comments on this post: Why does VSS 2005 Web service requires a share?

# re: Why does VSS 2005 Web service requires a share?
Requesting Gravatar...
Hi Thomas,

You can try Dynamsoft SourceAnywhere for VSS, the fastest SourceSafe remote access software. It is recommended by Microsoft. Take a look at:

Also, you can try SourceAnywhere Hosted, which is delivered as a SaaS application and fully managed by Dynamsoft. It integrates with VS 2005. The url is:


Catherine Sea
ps: I work for Dynamsoft.
Left by Catherine Sea on Jul 04, 2007 5:30 PM

Your comment:
 (will show your gravatar)

Copyright © Patrice CalvĂ© | Powered by: