General information
Category:
Source Safe Control
What makes the integration best with SSafe?
>Integration is best with SSafe - and it works ok with small teams on a LAN. Breaks down with laaaaarge projects and sloooow internet if accessed from outside. Look at your project and developer/access characteristics first.
>
>my 0.0002€
>
>thomas
>
>
>>If one is "starting out fresh", as I am, with implementing version control, which system would you recommend. I have read on here where people are successfully integrating Vault with VFP... but Vault is not free. I have also read that Git is considered to be a "DVCS", distributed version control system, whereas Subversion uses a "traditional, centralized model". I also just read that Vault now integrates with a SQL Server version control system from RedGate... something that would be very important in this environment.
>>
>>Honestly, my experience is minimal in this area... a little bit of exposure to Sourcesafe. But I gave it up because of what I perceived to be its limitations in handling vcx's, scx's... something that has been addressed here, and something that I will obviously have to revisit.
>>
>>
>>>Because forms, reports, class libraries, and other files are not stored as text, any source control program will have problems tracking changes to them. VFP ships with SCCText.prg that creates a text version of those files to ease the SCC issue.
>>>
>>>However, I would not consider Source Safe at this time. It has known issues and has been discontinued by Microsoft. Many people have turned to Subversion or Git, both free or to Microsoft's TFS.
>>>
>>>>Hi Friends,
>>>>
>>>>The sourcesafe 6 works well with Visual FoxPro? It tracks changes in forms?
>>>>
>>>>Thanks in advance
>>>>
>>>>Dionísio
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only