Altium NEXUS Documentation

Defining Version Control Preferences for Altium NEXUS

Created: July 18, 2017 | Updated: July 18, 2017
Now reading version 1.0. For the latest, read: Data Management - Version Control for version 4
This documentation page references Altium NEXUS/NEXUS Client (part of the deployed NEXUS solution), which has been discontinued. All your PCB design, data management and collaboration needs can now be delivered by Altium Designer (with Altium Designer Enterprise Subscription) and a connected Altium 365 Workspace. Check out the FAQs page for more information.

Parent page: Data Management Preferences

The Data Management - Version Control page of the Preferences dialogThe Data Management - Version Control page of the Preferences dialog

Summary

The Data Management – Version Control page of the Preferences dialog allows you to set up version control options such as Providers and SVN Executables. By default, the VCS Provider - SVN extension is installed. This extension delivers implementation of version control functionality through the use of SharpSVN. This implementation has full support for Unicode (multi-byte) characters in file names. As an example, this allows you to add files to your SVN VCS repository that include Russian characters in their names.

Access

The Data Management – Version Control page is part of the main Preferences dialog that is accessed by clicking the  control in the upper-right corner of the workspace then selecting the Version Control entry under the Data Management folder.

Options/Controls

  • Provider - lists the version control providers available.
  • Enabled - check to enable SVN - Subversion to enable the default provider.
Found an issue with this document? Highlight the area, then use Ctrl+Enter to report it.

Contact Us

Contact our corporate or local offices directly.

We're sorry to hear the article wasn't helpful to you.
Could you take a moment to tell us why?
200 characters remaining
You are reporting an issue with the following selected text
and/or image within the active document: