How to: Set up the Server that Runs the Visual SourceSafe Version Control System [AX 2012]
Updated: May 16, 2011
Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
This topic describes how to set up Microsoft Visual SourceSafe (VSS) as a version control system for Microsoft Dynamics AX.
To set up the server you must:
-
Create a new VSS database on the version control server.
-
Create a project.
-
Share the VSS database folder.
-
Restrict developer access to the system settings.
Note We recommend that you restrict access to the VCSdev.xml file to prevent developers from modifying global version control settings.
To create a new VSS database on the version control server
-
Open Microsoft Visual SourceSafe Administration.
-
Click File > New Database, and then click Next.
-
In the Location text box, type the path and folder name of the database, and then click Next.
-
Type the name of the new VSS database, and then click Next.
-
Select the Lock-Modify-Unlock Model check box to use the pessimistic concurrency model, or select the Copy-Modify-Merge Model check box to allow for concurrent development, and then click Next.
-
Click Finish.
To create a project
-
Open VSS. In the VSS database, right-click the root node ($/), and then click Create project.
-
Type a name for the project that will hold the Microsoft Dynamics AX objects.
To share the VSS database folder
-
Right-click the VSS database folder, and then click Sharing and Security.
-
Click Share this folder.
-
Click the Permissions button.
-
In the Group or User names pane, select a user group, a user, or everyone.
-
Select the Allow Full Control check box, and then click OK two times.
To restrict developer access to the system settings
-
Open Microsoft Visual SourceSafe Administration.
-
Click Tools > Options.
-
On the Project rights tab, select Enable Rights and Assignments commands, and then click OK.
-
Click Tools > Rights by project.
-
Expand the project nodes, and then select the Definitions node.
-
Select all of the developers in the users list, and clear the Check Out/Check In check box.
Note This enables read-only access to all developers, and the administrator keeps all rights.