Version control of distributed software

Like the subject says, I'm working on a way to control versions. I will be writing several small applications that will be used throught the company by 20-30 people. If I do an update or bug fix, I want a way to make sure everyone is using the most recent version.
I started writing my own, but thought I'd check and see if someone already has a solution.
Edit: clarity

Software Control Software!  Something like Tortoise SVN works wonderfully for this.  You just commit your code updates and then make everybody do an update.  They also have the option of sticking with the old code just in case they don't like your update.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Similar Messages

  • Lightweight Version Control and/or IDE ?

    Summary:
    I would like to know if anyone has any suggestions for a light-weight version control system ? A light-weight IDE would also be of interest (more advanced than TextPad, less complicated than Eclipse).
    I would have stuck this in the IDE forum, but it seems their isn't one.
    Details:
    Previously, I have been doing my Java development using a text editor (TextPad), and doing most everything manually. I like this approach, because I understand everything that is going on.
    I recently ventured out in the hopes of implenting version control. Going with what's popular, I set up CVS on my Linux server and access it using Eclipse on my PC. I would just continue using TextPad, but I like how Eclipse provides a nice GUI front-end for CVS functions.
    Unfortunately, I've found the whole CVS/Eclipse setup to be buggy and convoluted. I still don't have CVS set up quite right. I can't seem to tag anything with a version, and I still don't know how to properly set up access privelidges (for simplicity, I ended up using chmod 777 on all CVS directories and files).
    This whole setup seems to require intricate Linux, CVS, and Elipse knowledge. Now, instead of working on my Java application, I spend most of my time trying to better learn Linux, CVS, and Eclipse. Progress on my projects have ground to a halt. Every problem I encounter requires hours of research to resolve, and it often results from not understanding the complicated inner workings of one of these insufficiently documented products.
    In the end, I really just wanted some version control for my software with a user-friendly GUI front end. I have no wish to be a Linux expert, or a CVS expert, or an Eclipse expert. I just want to be a user, so I can get on with doing my real work -- Java programming.
    <rant>
    I find Linux in particular to be especially difficult to grasp. It's not that the O/S is complicated. It's that materials for learning are sub-par or nonexistent. The Linux community, as well as many other software communities, like to think of themselves as part of some elite club of experts they don't want others to join. To perpetuate this, there is a general lack of tutorials, GUIs, or helpful information of any kind. Take "man" for instance, the worst help facility ever created, which has never been improved upon.
    This would all be okay if I could simply use the non-existent CVS installer to install and configure CVS. But no, I have to do it all manually, from setting up the CVS server in xinetd, to editing the cvswrappers file (why is this not set up from the get go?), to changing iptables to allow CVS connections through the firewall. Simply trying to figure out how to set an environment variable is an exercise in frustration the first time. It took me probably an hour of research just to figure out that I needed to edit the file "profile" in the "/etc" directory because such information is not nicely documented anywhere.
    </rant>
    Conclusion:
    Ideally, I would like a SIMPLE version control system that I can just run on my Windows PC. Something with a GUI preferably, as managing large numbers of files from a command prompt is tedius. Likewise, a light-weight IDE, something less complicated than Eclipse, would also be of interest to me.
    Also, if you have any recommendations for a good Linux book, that would also be of interest to me. Such a book would probably be tailored to a specific flavor of Linux since each flavor uses different tools. I currently use Fedora Core, so a Fedora Core book would be preferable. I think I am probably stuck using Linux for a server, as my copy of Windows NT Server is hopelessly outdated, and Windows Server upgrades cost thousands of dollars I don't have (why don't they have an educational version of Windows Server?). I still regret spending thousands of dollars the first time.
    Thanks for any suggestions.

    Imho, CVS is a rather simple version control system, though I wouldn't want to access it using IDE plugins as they hide a lot of functionality. For an alternate frontend, have a look at WinCVS (www.wincvs.org) -- it's not that buggy.
    You could also try subversion as a replacement for CVS, but afaik, there's no reliable and comfortable GUI client available yet.

  • Preference for git over other distributed version control?

    Out of curiosity, and not to start a flamewar or anything...but, why does it seem like most Archers have an preference for git over other distributed version control software choices?  I tend to like Mercurial, as it was an easy transition from using SVN for so long, but reading the mailing lists, it looks like most of the Arch project development is moving toward git.  Is there something I don't know?

    elasticdog wrote:Would you say you like it more than Mercurial, or just now that you've been forced in to using it, it's not bad after the learning curve?  Which one do you use for personal projects?
    I do prefer git, after using mercurial for a quite a while.
    - Git is fast (very fast).
    - The format patch and other random porcelain are great.
    - The syntax and UI is a bit unruly, but once you get the hang of it, it's not a big deal.
    - Once very awesome thing for me is the ability to do localized in-repo branching, just checkout a local branch, and your tree changes to that branch. Do stuff, commit, whatever. Then checkout your other branch, and bam. You can diff and merge between local branches, create new ones, throw ones away, etc.. all within the same tree (no need for external clones).
    - The quick and easy rebase functionality is great too.
    I guess I would say git is powerful, but certainly arcane.
    I think mercurial got named branches a little while ago, so I haven't used them. I *think* they are similar to git branches, but I don't know for sure. The little I have read about them make them seem a bit funky.
    I prefer git, but mercurial is a fine choice too.
    I would say that pretty much everything out there besides these two sucks.
    ....and codemac is crazy by the way. map-my-scm-zealotry.

  • Poll - Which Version Control Software Do You Use With LabVIEW?

    I wish the forums had a poll feature. I created a poll in the developer community - Which Version Control Software Do You Use With LabVIEW?
    http://decibel.ni.com/content/polls/1818
    Edit: I just saw that there already is a poll for that
    http://decibel.ni.com/content/polls/1050
    =====================
    LabVIEW 2012

    julieann wrote:
    You can use a source control provider to share files among multiple users, improve security and quality, and track changes to shared projects. Use LabVIEW with third-party source control providers so you can check out files and track changes from within LabVIEW. See info. here.
    Looks suspiciously like someone trying to increase hits on their blog. A coincidence that it was posted the same day as the blog post?
    Message has been reported to the moderator. Laura can decide whether or not it's appropriate.

  • I'm a software tester for an in-house app at my company. version 10.0.2 is not cmopatible with some controls within our software. I need the v9.0.1 download which I know works with the controls. Where can I get it?

    I'm a software tester for an in-house app at my company. version 10.0.2 is not cmopatible with some controls within our software. I need the v9.0.1 download which I know works with the controls. Where can I get it?

    Well, if you need old versions of firefox you can find them on this site:
    - http://www.oldapps.com/firefox.php
    Best regards, G-Cloud.

  • Configuration version control software

    I know some people like to put their /etc under version control with CVS or hg or something, to make it easier to recover if they misconfigure something. I think this is kind of overkill, though. For one, you don't really need "distributed" or "centralized" version control, you just need to control the version. And for another, version-controlling the entire /etc doesn't really make sense considering that you're usually only working with a few files at a time, which you would generally control separately. So, I came up with the idea for a VCS specific to managing your system configuration. I'm going with the name Tessen for now since it sounds cool.
    The two basic concepts involved here are applications and snapshots. An "application" refers to a particular set of config files managed by Tessen. For example, the pacman application would own pacman.conf, makepkg.conf, and pacman.d (a directory). Ownership in this context means that it will automatically track changes to the contents of the files and folders. (Each application has an active snapshot, which is basically "the last one you saved or reverted to.")
    A "snapshot" is how an application's config files looked at any given time. A snapshot has a number (since it's not distributed, a simple autoincrementing integer will work), a timestamp (for obvious reasons), an action (to indicate exactly what caused this snapshot to be taken - for the user manually saving it would be "save", if it was installed by a package manager, "install", etc.), a note (if you feel like it - a good sysadmin would always have one), and the files' contents. (You can also add additional notes to snapshots after the fact, but this won't affect the note that was saved with the snapshot in the first place.)
    Anyway, the workflow would run something like this:
    "tessen newapp pacman pacman.conf makepkg.conf pacman.d". Tessen creates a new application named "pacman" that owns pacman.conf, makepkg.conf, and the directory pacman.d. (Tessen would automatically save a snapshot at this point consisting of the current contents of said files. That would be snapshot #1.)
    Make changes to the configuration, like using aria2c as the transfer command.
    "tessen save pacman -n 'set XferCmd to aria2c'". Tessen will take a snapshot of all the files owned by pacman and save that, making it #2.
    DOOM! You forgot that you don't have aria2 actually installed, and now that XferCmd is aria2c you can't install it! (This is just a contrived example.)
    "tessen revert pacman". Since you're at #2 but haven't made any changes, it will switch you back to #1. (If you had made changes, it would reset to #2 instead.) All necessary files will be reverted.
    Now you can "pacman -S aria2" and make sure it works this time.
    You could edit it manually to set it back to aria2 (which if you saved it would make it #3) but it's easier just to "tessen revert pacman 2". revert jumps back one step by default, but you can tell it to revert to anything. Then the next change you make would be #3.
    One major thing about the design I haven't quite decided would be how ownership is stored, and what to do if you change the ownership and try to revert to an older snapshot. That would be tricky to figure out. Still, what do you think about this approach?

    ewaller wrote:I think I'm missing something :-/
    I know the OP dismissed git and hg at the outset -- but why?  It seems to me they are ideal for just this sort of thing.  On this machine, I do have an Hg archive living under /etc.  Being Hg, it is simple to push that off to other systems and keep them synced (or not).
    Perhaps tessen could wrap git or Hg?
    The reasons I had for not using a traditional DVCS (as much as I love them) include:
    A VCS in all of /etc would manage your configuration as a whole. Tessen lets you manage each application separately without awkwardness.
    Also, there is stuff in /etc that isn't really configuration (I'm looking at you, /etc/bash_completion!). You could get around this by simply not "hg add"ing those files, but it does make it trickier. (Though in an ideal world, each app would store its configuration in a separate directory and things like the completion scripts would be in /share or /usr/share.)
    Finally, if you're using a DVCS so you can sync configuration, this would actually be better. For example, if you're trying to share the Apache and CouchDB configurations between your boxen, you have no way to keep out any other files you might have added (like, say, fstab).
    Really, it's mostly just that the concepts behind Tessen map more clearly to the problem than those in hg or git. At least in my mind. Although using a DVCS as the storage backend would be interesting...
    fukawi2 wrote:What language are you planning on writing this in?
    Probably Python. (My original concept would use SQLite as the database.)

  • Hello, I want to use version controlling software with Labwindows.

    Hello All.
    I want to use version controlling tool with Labwindows/CVI. Actually version controlling tools work for text files and by using the tool i can do version controlling of my .c and .h files in Labwindows/CVI project. But is there a way to do version controlling of .uir files also. Version control tool can detect the changes made in .uir file but is there any tool that can be used to compare and merge .uir files too just like text files operation for version controlling.
    Regards

    Hello Moshi,
    Personally I never understood how the integrated version control system of
    CVI works, but SVN (and TortoiseSVN) works fine with CVI projects.
    UIR files are treated as binary, as they should be, and that's about all.
    You could put the .tui file under version control instead, but I don't think
    it's worth the bother.
    Guillaume Dargaud
    http://www.gdargaud.net/

  • Version Control Software Recommendations

    Can anyone recommend a reliable 3rd party Version Control System to look after our Forms, Packages, Procedures, SQL Scripts etc.
    Without bashing Oracle's SCM too much we are finding it a little restrictive and there is very little information on how to get the best out of it.
    Merging and Version comparison isn't a must (one of SCM's better qualities) but it should integrate with a 9i DB for storing of the objects as BLOB's etc.

    Hi,
    Take a look at the Quest product called STAT.

  • Application size in terms of pages and performance and Version Control

    Currently I'm looking into the best way to version control our APEX applications. From other threads, it seems it's an area that leaves much to be desired. We are on the verge distributing a large APEX project commercially but I cannot find a suitable versioning method to support bug fixes and new development happening at the same time to the same set of applications. I just hope everyone out there realises versioning is a vital area of the development process and VOTES for it in the V3 poll.
    Anyway, enough of the my whinging. I did have a brain wave (quite rare !). What would the drawback be to have only 1 or 2 pages per application. This would allow a developer to always import the application at the start of work (ie from versioning software such as VSS or PVCS) and then export it at the end back into say PVCS. The application has everything self contained and correct versions etc.
    This would allow more developers to work on different areas at the same time as opposed to having many pages in the one application where developers could step on each others toes etc. I've considered importing/exporting pages but the fact you cannot lock shared objects means there is a possibility that if many developers are working on the same application someone will change something that affects pages other than their own. It would also be a nightmare to tie up different versions of of pages, shared objects, applications etc. Would there a performance problem with this method ? Incidentally, why can't TABS be shared/subscribed across applications. It means they have to be created separately in each application whereas things like Nav Bars and Templates can be shared across applications.
    Currently, my thoughts are that: bug fixing for a production release has to be in a separate stream (apex installation) from say new development work for the same set of applications BUT what this means is that the bug fixes have also to be manually applied in the new development stream - which is a considerable overhead (ie twice the work).
    Thanks for hearing me out - assuming you survived to the end !
    Any encouraging comments would be appreciated !

    Wim,
    I don't entirely understand the behavior. There should be little/no difference between the two cases. I'm assuming you have no indexes, which isn't recommended for such large containers anyway. Can you make your document set available to me so I can see if I can reproduce the behavior and look at it more closely? A single container, or dbxml_dump of a container is sufficient (both compress well).
    Contact me directly at george dot feinberg at you know where.
    George

  • Version control tool for Mac OS X?

    Hi all
    If using labview on Mac OS X, 
    do you have some version control tools to recommend?
    Thanks  a lot

    As far as i know, LV for Mac does not integrate with source code control provider. LV for Windows has two requirements for this:
    a) Professional Development Environment
    b) A source code control provider compatible to the Microsoft Source Interface
    There is still always (Mac, Linux and Windows alike) the possibility to control source files using the SCC providers client software.
    Many open source project SCCs like CVS or Git integrate, at least in Windows, in the File Explorer.
    I recommend you to research possible solutions like this for Mac.
    The next question is if you want to use a distributed SCC or a local one. Depending on this, you will have to setup a network server with compatible provider (e.g. RhodeCode).
    LV provides both a Diff and Merge tool as EXE (Professional). I am not sure if this is also true for the Mac version, so look for "LVCompare" and "LVMerge".
    hope this helps,
    Norbert
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • Regarding version control

    Hi,
    Could u please help me out in giving some ideas of version control in sap?
    First let me give some example as follows:
    First if i develop something in the developement server then later when i transfer to the QA server and later to production server then is there any change in version.
    Please give me a details of this issue????
    Thanks,
    Batista....

    hi priya,
    Version Control
    Version control is a mechanism that helps maintaining the revision history of a development resource and tracking the changes done to it. It defines a set of constraints on how a development resource can be changed. A development resource that complies with the constraints defined by the version control is called a versioned resource. When a versioned resource is modified or deleted, a new version is created for the resource. A unique sequence number is associated with each version of the resource created in a particular workspace. This sequence number identifies the order in which the versions were created in that workspace. The DTR graphically represents the relationship between the different versions of a versioned resource in the form of a version graph.
    For the representation of version graphs, this document follows the conventions shown in this figure.
    The figure shows the meaning of the symbols in the version graph.
    The following changes are tracked by the version control mechanism of the DTR:
    ·        Addition of the resource to the repository
    ·        Modification of the resource in the repository
    ·        Deletion of the resource from the repository
    In all the above cases, a new version of the resource is created.
    Production Delivery
    Packaging
    To deliver your product, you have first to package it. There are different packages you can use for shipping your product to your customers:
    &#9679;      Software Component Archives (SCAs) – this is the standard way to deliver software for the SAP NetWeaver platform.
    &#9679;      Software Deployment Archives (SDAs) – for top-level applications you can deliver only the executable part of the software. You can directly deploy the SDA file.
    &#9679;      Public Part Archives (PPAs) in Development Component Interface Archives (DCIAs) – for reusable components (Java EE server libraries, Web Dynpro components, Visual Composer components and so on). You can deliver only the metadata of the components. DCIA can be included in SCA file too.
    How to do that?
    Using the command line tool provided with the SAP NetWeaver Composition Environment you can:
    &#9679;      package a collection of components into an SCA including only the deployable archives. This is required if you do not want others to reuse the delivered components.
    &#9679;      package a collection of components into an SCA including the deployable archives and the corresponding interface archives. This allows customers to develop against these components. Those customers can directly import the SCA into their own SAP NetWeaver Development Infrastructure (NWDI) or into an SAP NetWeaver Developer Studio local installation.
    &#9679;      package the public parts of a component together with the required metadata into a DCIA (and further into an SCA).
    &#9679;      include source code into an SCA.
    &#9679;      unpack a deliverable archive and drop the result into an existing version control system for example, or directly import them into an existing Design Time Repository (DTR).
    Delivery of Source Code for Further Customization
    In addition, you can deliver source code to your customers to allow further customizing or add-on development. The deliverable archive may contain sources for:
    &#9679;      individual development components (DCs).
    &#9679;      a collection of development components, for example a whole software component (SC).
    Example
    A customer can add a new source compartment to an existing configuration, and then locate that compartment in the file system where it is accessible by the version control system in charge. Then he or she extracts the sources with the command line tool to the compartments root directory and refreshes the configuration in the SAP NetWeaver Developer Studio. The compartment tree is populated with components from the archive. Afterwards, the customer may put those components under version control. Deliverables that contain only individual components may be treated accordingly.
    This mechanism may also be used for other purposes, for example for setting up a simple backup and restore mechanism for components in Developer Studio, or sharing DC sources without having a central version control system: a developer may pack a compartment and store the resulting SCA on a central share or backup system. Another developer may take that SCA and import it.
    Limitations
    Note the following limitations connected with this kind of source code delivery:
    &#9679;      There is no support for handling conflicts when different actors in a delivery chain develop independently in the same source code. You cannot prevent the customer from modifying delivered sources. When you ship a new version of the sources, there is no special support for updating and no support for merging the update with modifications done by the customer. You and the customer have to agree on a process how those conflicts are handled. For example, the customer can decide not to import the update you deliver directly into the active development line, but to unpack the delivered sources to some unconnected sandbox system and perform the required merges manually.
    &#9679;      When you deliver source code to customers, it is important that you also deliver the required libraries and generators that are needed to build these sources. For example, it may be necessary to ship some archive compartments that contain used components.
    &#9679;      There is no support for delivering deletions in a new version. If a source file was deleted, the customer has to manually ensure that the file is also deleted in the Developer Studio or source code management system.
    &#9679;      If a customer prefers to work with the SAP NetWeaver Development Infrastructure (NWDI), this customer cannot directly import the source delivery package into the NWDI landscape. Between NWDI landscapes at different places, sources usually are exchanged through a more sophisticated export format that contains not only the pure source code, but also the versioning meta information of the exporting DTRs. This ensures that the importing repository can detect conflicts that arise due to modifications. If this versioning information is not available, the only way to import source deliveries is to unpack them to a file system and manually put them under version control with the Design Time Repository perspective of the Developer Studio. In case of an update, the customer would have to check out all affected files, merge them with the new versions from the source delivery, and finally check them in as a new version.
    More information: Composition Environment Command Line Tool
    see this url
    http://www8.sap.com/businessmaps/0134713B1D6046C59DE21DD54E908318.htm
    thanks
    karthik
    reward me if usefull

  • When downloading the latest version of Itunes, the software is not accessible anymore and needs re-installing. How do I prevent that when re-installing I will not loose the numbers stored on my harddisk?

    When downloading the latest version of Itunes, the software is not accessible anymore and Itunes seems to need to be reinstalled. How do I ensure the Itunes music is not lost and my pc is still recognized by Itunes store?

    Crikey. Okay, that's part of the Gracenote SDK (that iTunes uses to go online to get album and track information for imports).
    Let's take the message at it's word. If the file is damaged, we may be able to get past this by removing it from the iTunes program files and then doing a repair install of iTunes.
    In Computer, open Local Disk C:\ (or whichever drive you've got your program files installed on).
    If you've got a 32-bit version of Vista, open the "Program Files" folder.
    If you've got a 64-bit version of Vista, open the "Program files (x86)" folder.
    Open the "iTunes" folder.
    Drag the gnsdk_sdkmanager.dll file out of the folder and onto your Desktop.
    Restart the PC. Head into your Uninstall a Program control panel, select "iTunes" and then click "Repair".
    Does the repair install go through properly? If so, can you launch iTunes now?

  • Version Control for adobe forms

    Dear All,
    We have a situation where we already go live with version 0 of our adobe form. Now, we have an enhancement to the form i.e.: some new functionalities and new field. Previously we have tried to transport the new changes to the production without any version control and those processes that have been already started prior to the new changes encounter error when the user continues the process.
    I am wondering how do the version control works and any documentation on how to configure it?
    Thanks in advance
    Regards,
    Bryan

    Hi Brian,
    Here is some information that I found in the IMG on Create ISR Scenario...
    Create ISR Scenario
    Use
    In this IMG activity, you create an ISR scenario that has a one-to-one relationship with a form scenario. To be able to use a form scenario in a process, one ISR scenario must exist for each form scenario. The ISR scenario and the form scenario must be linked with each other. You make this setting in Customizing for HR Administrative Services in the IMG activity Link ISR Scenario with Form Scenario.
    In the form scenario, you define primarily the basic set of form fields and their processing through the backend services. In the ISR scenario, you specify the definition of the user interface. You also specify which form is used for the display and how the layout of this interactive form is designed. You use interactive forms based on Adobe software to create and process the forms.
    ISR scenarios and form scenarios are version dependent. The version numbers of the ISR scenario are assigned automatically. Note that a form scenario must have exactly the same version as the linked ISR scenario. For this reason, you should always create a new version in the ISR scenario first and then use the same version number when you create a version in the form scenario manually.
    Note
    If an ISR scenario or form scenario (with an existing version) has already been used in a productive process, you should not change the configuration. If you want to make changes to a process or an ISR scenario or form scenario, you should always create a new version, and only ever use that new version in the future. In this way, processes that have been started can be concluded with the old version and new processes can be started simultaneously with the new version.
    This is from the Create Form Scenario documentation...
    Create version
    Form scenarios are version dependent, which means that there is at least one version of each form scenario. Versions are linked with processes. Since processes can vary, you must also be able to adjust the associated scenarios. To be able to provide different forms for process variants, you create versions.
    You can still process and change an existing version at a later point in time. Once a version has been used to execute a process, you should not make any more changes to this version; instead, you should create a new version.
    The form scenario and the (linked) ISR scenario are both version dependent. They must always have exactly the same version numbers. Note that the version number of the ISR scenario is generated and cannot be entered manually. When you create a new version in the form scenario, you therefore have to use the version number generated in the ISR scenario.
    If you have already made extensive Customizing settings for the form scenario and want to create a new version based on the settings, you should use the IMG activity Manage Form Scenario.
    Hope this helps...
    Cheers,
    Kevin

  • Can we use RoboHelp with Eclipse as version control?

    Im am using RoboHelp 7 in the Tech Comm Suite in a Windows XP environment.
    I see a lot of information on using RoboSource as versionn control, but I'm not seeing a lot of information on other third-pary version control software.  I did see one posting that suggested that if you are planning to use third-party software, you should uninstall RoboSource first.  I can't seem to figure out the following:
    How do you determine if your version control (Eclipse) supports Microsoft SCC API?
    How do you get RH to recognize Eclipse? Even though I uninstalled RoboSource Control 3, it still shows up in the Select Version Control Provider
    Are there step-by-step instructions anywhere that show how to get RoboHelp to recognize third-party software?
    As always, thanks for your assistance.

    Colum,
    Thanks for recommending that I visit Peter's web site.  It has a great page on Eclipse.  Wish I had read it before I was shoved kicking and screaming into using it.  However, it did stop short of providing me with information to troubleshoot the problems I'm having with Eclipse and RH 7.  I sent him an e-mail from the site and hope that he will be able to answer it.

  • Opening Project First Time from Version Control.  RoboSource Node

    Four writers have upgraded successfully.  My fifth is having issues...
    She has Serena Dimensions SCC installed as well (another source control product - used by Applications, not the authors or Infra.
    Problem: When she is establishing the root path (and the Browse RoboSource Node window opens, but it does not populate, even after 20 minutes.  Reboot did not work, neither did manually removing Serena Dimensions SCC.  I have verified that she has a connection to the database (via RSC Explorer) and can see the project (as well as the RH7 version of the project).  We have
    These are the instructions... (screenshots not included).  She's hanging up on
    1.1    Using a New Project for the First Time
    IMPORTANT NOTE:
    The author must have local administrator rights on the machine.  If the user has a privileged account, they must set up full local control of their work folder (specified in 1.1.2.8).
    1.1.1    Install RoboHelp and RoboSource Control
    1.    Download appropriate software packages, including all patches, from Adobe.
    2.    Launch RoboHelp Installer.  Select the following options for installation:
    o   RoboHelp for HTML
    o   RoboSource Control (Client)
    o   CS4 Script Extender
    INSTALLATION NOTES
    Installation of each component is separate and may take up to 30 minutes.  You do not have to install RoboHelp for Word.
    Only select the Client Install for RoboSource Control.
    3.    Install all patches in the order specified by the vendor.  Check with the technical communicator on which version is currently in use for patching.
    1.1.2    Open the Project
    1.    Launch RoboSource Control.
    2.    Establish a database connection per section 3.3.1.
    3.    Close RoboSource Control.
    4.    Launch RoboHelp 8 for HTML.
    5.    Click Open under Recent Projects under the main frame (do not use title bars).
    6.    Click the Open Project from version control button (shown below).
    7.    Make sure that RoboSource Control 3.1 is highlighted as the Version Control Provider and the checkbox for “Make this my default selection” is checked.  Click OK.
    8.    Configure the Source Control system as follows:
    Connection:  PROD
    Root Path: Click the … button and navigate to the (project name) root in the database and click OK.  This may take several minutes.
    Connection Mode:  Online
    Get to Local Path:  Click the … button and navigate to your Data folder.  Select Make New Folder under Data and give the folder a unique name to help you identify the files as for the Support KB in RoboHelp. 
    9.    Click OK when you have configured source control.  A copy of the database is now being downloaded to the path you specified.  This may take up to 20 minutes. 
    You can verify that installation is proceeding either by watching your local path fill with files or keeping an eye on the CPU usage of the RSO3MiddleTierService and RoboHelpHTML files under Task Manager.
    10.  Once transfer is complete, highlight Tier1KB.xpj and click Open.  It may take several minutes to open the project the first time.  It is typical for the snippet file to check out the first time you open the project and the first time each day that you save all project files.
    11.  Once the project is open, set Version Control properties:
    a.         Select Tools > Options.
    b.         On the Version Control tab, select all options.  This will prompt the user on each version control action they take.
    12.  Test a check out/check in to validate correct installation and source control operation.

    It's the settings in miscproperties in the XPJ and it works in TFS just fine. I'ts as follows:
    <miscproperties>
      <matchedpair>
      <name>vc::provider</name>
      <value>Team Foundation Server MSSCCI Provider</value>
      </matchedpair>
      <matchedpair>
      <name>vc::agent</name>
      <value>MSSCC</value>
      </matchedpair>
      <matchedpair>
      <name>vc::database</name>
      <value>http://ap-gda113-tfs-a:8080/tfs/centric|NB-WWEELDEN|ITS\Wweelden</value> <- Add the TFS URL, your workspace name and your domain name.
      </matchedpair>
      <matchedpair>
      <name>vc::cookie</name>
      <value>$/BV - MVV/Main/Tools/Documentatie/mvv-beheerders</value> <- The location of the project in TFS.
      </matchedpair>
      </miscproperties>

Maybe you are looking for