Information générale
Catégorie:
Source Safe Control
Versions des environnements
Thanks for the info Thomas. I will take these ideas into consideration. It sounds like in the environment it might work.. there are multiple virtual servers... but the development is done on local workstations.
>We work with the project manager a lot - check in/out with hooks for Scctext.
>Also each dev has his own project files - another weak point that is circumvented.
>
>As all dev machines are virtual machines hooked together on fast virtual cards
>with the SSafe machine and a build server, most of the SSafe weak points don't touch us.
>
>In this setup SSafe works great - 7 devs and libraries scattered through many projects.
>
>regards
>
>thomas
>
>>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
Précédent
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement