I realize this is a major longshot, but it never hurts to ask. We are considering upgrading from VSS to Vault and currently have a program written to access our current source code repository via the ssapi.dll (sourcesafe API) interface.
Is there a way to configure/hack vault to intercept calls through this interface to itself instead of sourcesafe? I'd love to avoid having to update this app to continue using it after we switch to vault.
ssapi interface
Moderator: SourceGear
Sorry, the Vault Client API is a totally different animal than VSS's interface.
There are no OLE interfaces, but a set of .NET class libraries. The Vault Client API (http://www.sourcegear.com/vault/downloads.html) does come with the Command Line Client Source code so there are samples for pretty much any operation done by the Command Line.
There are no OLE interfaces, but a set of .NET class libraries. The Vault Client API (http://www.sourcegear.com/vault/downloads.html) does come with the Command Line Client Source code so there are samples for pretty much any operation done by the Command Line.
Jeff Clausius
SourceGear
SourceGear
I assumed as much, I just thought there was a small possibility of a "substitute VSSAP.dll file that maps the commands over that could be replaced in that app directory. Oh well, so much for hoping.jclausius wrote:Sorry, the Vault Client API is a totally different animal than VSS's interface.
There are no OLE interfaces, but a set of .NET class libraries. The Vault Client API (http://www.sourcegear.com/vault/downloads.html) does come with the Command Line Client Source code so there are samples for pretty much any operation done by the Command Line.
Thanks anyway.