These instructions describe how to setup a 2nd and subsequent developers to use A VCS Master. It presumes that the VCS already contains the LANSA Repository.
Note: the most efficient way of installing the Visual LANSA Independent System to a VCS Master is to perform a Custom Install and on the options for Initialize Database and Partitions only chose Example Partition Definition. This is because the whole partition will be replaced anyway. Other partition initialization like Visual LANSA Framework need to be done after the partition has been replaced with the VCS Master data:
Either the install will finish here or start the Visual LANSA Independent System which is to be connected to your VCS Master. If it's a completely new install the logon will display something like this:
Populate VCS Working Folder
Once the Development Environment is displayed, show the Version Control tab by clicking on this icon:
Right click on the Active Partition and click Show in Windows Explorer:
Navigate up one level to the VersionControl directory and then copy the whole of the path. Paste this into the working folder in the VCS:
Right click on DEVPGMLIB and choose Get Latest Version.
Go back to the Visual LANSA Development Environment and perform a Get latest Version on the System Information. This will bring in, amongst other data, all the partitions that are in the VCS Master.
Close down the Development Environment and login to the new partition. Perform a Get Latest Version on the Active Partition.
LANSA and the VCS are now linked up together. All objects will be unavailable to edit now as they are not checked out from the VCS. (This presumes you use the Check Out/Edit/Check In concurrent development style of version control) If you open an object it will display this message:
If you check it out from the VCS you will be allowed to edit it.
If you use the concurrent development style Edit/Merge/Commit, then of course the objects are always editable and you must resolve the status of the objects using the VCS.