Binding to SourceGear Vault

[Carsten Pedersen]

Hi,

We have used Flare since is came out, and now also Blaze. We have been extremely patient until now regarding the Source Control
integration. We waited many versions, and when it came it was extremely buggy.

But now running Flare 5 and Blaze 4 we would like to get this working.

That said, the problem is probably on out side since we are totally unable to bind to out SourceGear Vault database (like in the first versions).

So please talk me trough it...

* I have made a Blaze project, and all is fine.
* Now I want to add this to Source Control, and goes to the Project -> Project Properties dialog.
* Selecting Source Control tab and and presses Bind Project.
* Then I select Source Code Control Plug-in, and SourceGear Vault is listed in the Provider list as expected.
(now the trouble start)
* Clicking on Browse opens the Vault Add to Vault Folder dialog.
* By default the Project to add is set to my Blaze project name, and the Add project from working folder: points
to the location on my local PC, all as expected.
* But when I click OK nothing happens, the Project name stays empty in the Bind Project dialog
* When selecting OK SccOpenProject failing with error code -2 (The project is unknown.)

What am I doing wrong!

-cpede

[peterbrown05]

I am having the same problem with Flare 6.0 <---> Vault 5.0.3 (18802)

Did you find a solution?
cheers
peteB

[Carsten Pedersen]

No,

I managed to get MadCap and SourceGear technical support to talk together. And they exchanged some
emails, but did not come up with a solution.

As far as I remember it ended up with SourceGear tested their code with Flare, and found that even the
most common VSS calls did not work. And therefore no integration with Vault.

But for some reason there is no one at MadCap that takes this seriously. I'm sure that it is a bug in
Flare that just needs to be corrected. Very disappointing for us. I purchased Flare so that my application
specialist could write manuals and help. But this job is much more difficult without integration with
source control.

Hope someone at MadCap can take some action on this

-cpede

[RamonS]

Way back when this functionality was announced I recommended to implement it in a way that Flare does the integration through shell commands. That way it can be easily adjusted to any source control system that supports shell commands. The disadvantage is that it also can be easily goofed up and may cause a support issue. Instead MadCap chose to implement it by using a closed source 3rd party API that given the complaints in this forum works more often not than it does. I think there is some value to using the API as I assume that it works out fine for MadCap and those users who do not complain. Nevertheless, I renew the call to MadCap to add an option to implement source control integration through shell commands that can be freely configured. Add a reset function to go back to the standard calls that are available from product documentation of source control vendors. I have used that in different contexts and once it is set up right it works reliably. This is the same approach that many build scripts use to get code out of source control systems for compile.
I also often stated that I think documentation should be treated in no way different than source code. Would anyone consider an IDE as fit for production when it has such shaky source control integration? I doubt it. For now the only recommendation is to make file copies frequently and use external tools to connect to source control.

[peterbrown05]

bump... i'd still very much like to see this issue addressed. We are having to manually check files in and out of vault and this has led to the obvious problems where stuff hasnt been checked in, or in some cases edited by multiple people without source control leading to loss of data....

please re-evaluate the options here and help us integrate to vault.

[Carsten Pedersen]

I just tested in v7, and it still doesn't work.

Come on guys, please spend the 2 hours installing the SourceGear Vault client, and debug your software, and correct the errors.

-cpede

[peterbrown05]

agreed; ive just tried v7 and it looks like we "get further" than in v6 but still not working.
would love to see this fixed....

[RamonS]

The bitching....errr, complaint page is located here:
https://www.madcapsoftware.com/bugs/Submit.aspx

[GaryUK]

Hi, has anyone had any joy with this since 2010? I have just upgraded to 9.1.2 and I'm still having no luck. I also have the latest version of Vault.

I managed to get the project name field to populate by first checking the project manually into Vault, but now I get the following message:

"Adding: D:\Trunk\Source\Help\Paragon5.8Adding files in folder: file:///D:/Trunk/Source/Help/Paragon5.8/
Source Control: SccOpenProject call failed with error code -2 (The project is unknown.)
Source Control: CustomScc:AddFile - call failed with error code -2 (The project is unknown.)

The source control operation finished with warnings and/or errors. Press Close when you are done reviewing the messages."

Regards,

Gary