Working with Version Control in AcuBench

The AcuBench interface to version control software allows you to define commands that call your version control system directly or that execute your version control batch files. These commands are placed on the Version Control menu item that is accessed when you right-click a project or file node in the Workspace window.

When you select and run a version control command, AcuBench passes the defined command string and arguments to the Windows command shell for execution. By default, the command is echoed to the AcuBench Output window, which is also used to display console messages from the version control system.

Note: If your version control system does not have a Windows command-line interface, it cannot be accessed through AcuBench

When adding version control commands to the AcuBench interface, keep in mind that there are some commands that are better issued from outside AcuBench, or after AcuBench has been shut down. For example, changes to a particular program or file can easily be committed to the version control repository from within AcuBench. But a project commit (writing all changes made to a project to the version control repository) is better issued from the command line, after AcuBench has been closed, to ensure that all changes to the workspace project file (.pjt) have been written to disk.