Using Vault via an application that requires an srcsafe.ini

cornishe · Post by **cornishe** » Tue Mar 25, 2008 4:02 pm

Is there a way to build an srcsafe.ini file that in turn will be used to connect to Vault?

We've purchased an ERP which has VSS integration in its studio but requires a source safe srcsafe.ini file.

Thank you,
Abbie

lbauer · Post by **lbauer** » Wed Mar 26, 2008 7:40 am

Could you explain a little more about what you'd like to do -- are you trying to to have this ERP system communicate with a Vault Server?

cornishe · Post by **cornishe** » Fri Mar 28, 2008 12:21 pm

The ERP uses a forms and objects database to store all the forms for presentation and the IDOs (Intelligent Data Objects-- object wrappers for tables, and methods for sp's, etc.). Forms and Objects can be created and customized. The Studio in which you manipulate these objects has the ability to check-in/out the object or form from VSS every time you modify it so that you can easily maintain your history. If the ERP goes down, all production and sales will be affected so of course version control is a big deal. The SourceSafe integration piece asks for

Path to srcsafe.ini
VSS Project Name
User
Password

We are current users of sourcegear for our web team and rather would like to continue with this product and add licenses if possible rather than be forced to VSS.

Does this explain enough?

cheers,
A

cornishe · Post by **cornishe** » Tue Apr 01, 2008 11:08 am

bump.

lbauer · Post by **lbauer** » Tue Apr 01, 2008 12:17 pm

If this application was specifically designed to be used with SourceSafe, then I don't think there's much we can do to get it to integrate with Vault.

Some applications allow for other source code control providers. Does this one?

Also, you might be able to work with this application without integrating the development environment. It might be possible to use default GUI client to add, checkout, and check-in files, but still do your work in the ERP application. The folder in which you do your ERP work would be the working folder for the Vault client.