Hi Hank,

We will be setting up test boxes to test both Vault and Subversion in the near future in order to decide which product to use internally. Is your configuration information for VFP with Vault available anywhere else other than the Vault forum?

Tia,
Tracy

>We've used Vault for about a year now, after 3+ years with SOS/VSS. What a relief it has been! It is fast and reliable. On the Vault forum there's a message I put up there detailing the settings required to get the expected usage in VFP.
>
>Hank
>
>>Hi, Goran.
>>
>>>We are not building a code management tool here at all, we are building a front end to one (probably ClearCase or Harvest) we currently make use of VSS only because it came with VFP when it was still part of Visual Studio and haven't bothered to change because it was able to satisfy our needs... this was fine when the team was only 5-6 people; not so any longer.
>>
>>That sounds a lot better. :-)
>>I know you are not improvising at all, so I guessed you were probably not wishing to reinvent the wheel. Did you take a look at Vault? I have very good references about the product, although I just used the client a couple time while doing consulting at other teams. What's interesting about Vault is that it looks and works almost like VSS, but without most of it hassles. Among other things, it allows you to migrate all your VSS content, and it uses SQL Server as the repository, allowing for transactional check-in sets.
>>
>>You may take a look at:
>>http://www.sourcegear.com/vault/
>>
>>I'm not 100% sure, but I guess VFP should integrate exactly as VSS does, as it respects most interfaces. In any case, it is true that VFP integration is not the best possible approach...
>>
>>>Harvest or ClearCase are both vastly superior tools, and as you quite rightly point out there are a host of Open Source tools out there that we could use. Though being a large corporate (by Australian Standards) we can't just go out and use whatever we can get our hands on - in fact many of us can't even install software onto our own workstations ;-)
>>
>>Oh... I know about this. I'm just finishing a 10 months project at a big Telco here where I was forced to use VSS for my 30 people team, and it was simply a nightmare, but we have to get over it. Indeed, as part of my final report, I'm doing a strong recommendation to switch from VSS to Subversion. It is not because it is free, but because it is a high quality product with an incredible community and support. I'd recommend you take it in consideration. It is the evolution of the widely popular CVS.
>>
>>>So we decided that we needed a solution that would allow us to move off VSS onto something (anything) better and would still integrate with the VFP IDE. Fox is great in that we can write out own front-ends to pretty much anything that the IDE can do so with that thought in mind we decided it was time the project manager got a much needed enhancement. The goal is to allow each developer in the team to continue to work within VFP but have the code management (done by the SCM toom) handled automagically - and allow the testing and packaging teams to build and test the regular releases of the system without having to spend many ours copying classes from one developer's VCX to the reference VCX and so on...
>>
>>Are you using some kind of continuous integration tool? I'm working on a sort of CruiseControl.vfp for a customer of mine (this is my comeback to the VFP arena this year, indeed). I'll let you know how it goes. It will be an Open source implementation, and if you are willing to check I guess you can provide very valuable feedback.
>>
>>Best regards,