Version control: Create

To bring a USoft application under version control for your team, you must first put it in place by taking explicit one-time action. This is referred to as Create.

To create version control for a USoft application in Development:

1. In the USoft application (USoft Definer, USoft Service Definer...) that you want to bring under version control, from the tool menu, choose Tools, Version Control, Version Control Configuration. This dialog appears:

   

2. Click the Create button. Specify the file directory where you want the files for version control to be written to initially, then click Save.
3. Inspect the result on the file system. See that files have been created for all objects in your repository. See also that at the top level, a file has been created named

   application.usv

   where ".usv" is for "USoft version control" and application is the abbreviated name of the USoft application, for example, for USoft Definer:

   USD.usv

4. Set up a Git (or other) remote repository. Arrange for the tree of files that was the result of Step 2 to be uploaded initially to that remote repository. This upload step is not specific to USoft. It works exactly the same with any other set of files that you want to bring under version control.
5. Make sure all your USoft team members have a powerful enough computer or laptop to run a local working copy of the USoft repository (the set of RDBMS tables that hold your development work). Click here for an indication of hardware and software requirements.
6. Instruct each team member to set up the local RDBMS and to set up the connection to the remote Git (or other) repository. These two steps are not specific to USoft.
7. Point out to team members the location of the "application.usv” file. They need this information when they Connect.

Now, each team member needs to perform the Connect operation initially as a one-time action. From that time onwards, your team is all set to develop against a version-controlled USoft repository, and version control is largely automatic. Team members pull files that contain changes made by others. USoft automatically notifies them that they need to synchronise their local working copy of the USoft repository (the RDBMS tables) if there are any changes that they have not synced yet. When a team member has finished work on a fix or request, this team member pushes this work to the remote tree so that it becomes available to the others.