Frequently Asked Questions
TeamCoherence is one of the easiest to use Configuration Management tools available today. However, if you are having problems with TeamCoherence, or just want to find out more before downloading, please consult the following before requesting support or information.
Additional information, and electronic documentation is also available online from the documents section of the relevant products.
What are the limitations of the Evaluation version?
All functions, including the full UI, API, IDE integrations, and command-line, are enabled in the evaluation version to enable you to fully evaluate the modules of TeamCoherence. There are limits, though, on the capacity of the evaluation version. These are listed below:
- Version Manager: limit of 10 revisions per file. No limit on repository size.
- Tracker: limit of 50 issues
- Builder: 5 Build Objects per file
If you reach any of these limits, we can send you a temporary license to override them during your evaluation.
How do I integrate Beyond Compare as an alternative Difference Viewer?
TeamCoherence Version Manager supports multiple Difference Viewers on a per-filetype basis, as well as a default Viewer. To integrate Beyond Compare as the default Difference Viewer:
Start up TeamCoherence Version Manager
Select Tools/Options/Difference Viewers
Select the Beyond Compare executable as the Application
Enter "$LF" "$RF" /FV in the Parameters edit box
That's it. If you want to specify Beyond Compare as the Difference Viewer to use for specific file types, click on the Add button and enter the same details for each file type.
I check out a file in the GUI, but the change is not reflected in the Delphi IDE
This is a common question. The answer is that the TeamCoherence GUI and the IDE integration are actually separate instances of the client application (or a portion of it). The other instances will be updated to reflect the changes, but this is not an instantaneous change as it is carried out when the Server sends periodic updates to the connected clients.
Does TeamCoherence require the server to run?
Yes. TeamCoherence was designed from the ground up to be client-server. The client communicates with the server using TCP, so you can access repositories whether they are running locally, on a network, or half way round the world. However, you can also run the client and server portions of TeamCoherence on the same machine.
This also applies to the Personal edition of TeamCoherence, and to Tracker.
What is your upgrade policy?
Licensed users are entitled to free minor upgrades to the version of the software they purchased a license for. A minor upgrade is defined as a release of the software where the minor version number as viewed in the About Box for the software is increased. Minor upgrades normally include bug fixes and small enhancements.
Users who include maintenance in their initial purchase are entitled to a year of free upgrades (major or minor) for thenumber of licenses they have included maintenance for.
Users who do not include maintenance in the original order can continue to use the software (including minor updates for the version they purchased) for as long as they want, but major upgrades will be charged for.
To keep track of your licenses, and current maintenance levels, please visit our Customer Services Portal at:
Is there a command-line interface?
Yes. The command line tool for Version Manager is installed with all releases of TeamCoherence.
Can I let multiple users work on the same file?
TeamCoherence supports both parallel and serial development. With parallel development multiple users can lock a file and can thus make changes to local copies of the same file. With serial development, only one user can lock a file at a time.
Parallel / Serial development is defined at the server side and is normally configured by the System Administrator. There is also the option of running in a mixed mode. In this case the server is configured for Serial development but this can be overridden on individual files to allow multiple locks on these files only.
How can I move a file and its history from one folder to another?
Select the files you want to move in Version Manager and drag them to the target folder. The files and revision history will be moved to the new folder. Alternatively you can use simple Cut and Paste via the clipboard to do the same thing.
Remember that the default working path for the files will be inherited from the folder they were added to and may not relate to the original source folder.
How do I share files across projects?
Select the files you want to share in Version Manager, hold down the <Ctrl> key, and drag them to the target folder. Alternatively, use Copy and Paste.
Remember that the default working path for the shared files will be inherited from the folder they were added to and may not relate to the original source folder.
A common practice is to create a separate project specifically for shared files. The files are originally added to this shared project, and shared with other projects as required.
How do I merge a branch revision into the tip?
To merge changes made in a branch revision into the tip: Check out the tip revision to make it writable. Select the Branch revision in the Version Manager and select Action/Differences/<filename>. This displays the difference viewer to show the differences between the two revisions. Use the difference viewer to merge the changes (see the help file). Repeat the process for each file in the group. Finally check in the tip revision.
How do I switch off the insertion of comments at the top of source files?
By default, TeamCoherence will insert a header comment in all pascal and C++ source files. This is used to allow quick viewing of the revision history of a file while it is being edited. This can be switched off by Admin users by selecting Tools / File Groups... and clicking on the Header button.
Note that this does not affect normal keyword expansion which is defined in the File Groups section of the same dialog box.
Module has open descendants or linked modules, Cannot reload
This is a known problem with Delphi and C++Builder. Basically, Delphi is opening the linked form in the background but is not listing the 'hidden' form in the OTA. Borland know about the problem, but are not intending to fix it. The same problem will occur in all addins that attempt to reload these kinds of files.
How do I move a repository to another server?
It is a relatively simple matter to move a repository to a different server. Follow the steps below:
Shut down the existing repository service and backup the files
Copy the files to the new server
Install the TC Server on the new machine
Create a new repository instance and point it to the copied files
Start up the new repository
If required, update the clients to point to the new repository
If you are using a CD to copy the files between servers, make sure to clear the read-only flag that may be set on the copied flags.
If you are using Visual Studio .NET, and the repository is moving to another server, you may need to delete any .suo files associated with your solutions that are archived using TeamCoherence.
Service will not start automatically
This can be caused by TeamCoherence Server being installed on a Subst'd drive. Because there is no way for TeamCoherence Server Configuration tool to determine what the real path is, the service is configured to run using the substituted path.
At boot time, if the Service Manager cannot locate the service binary, the service will not be started. In other words, the Server should be installed on a drive that is available at boot time on the machine in question.