Here is the process normally used for the management of versions with Visual Guard .Net :
• At the beginning of the development of the application the Visual Guard repository is created in a development base. In this repository the development team define the roles, permissions and the permissions sets.
• When the development and the test phase are finished then the development team will define, with the help of a Visual Guard .Net wizard, what is going to be deployed and will generate an export file. This export file can be exported again in another repository thanks to the same tool. This tool can be used as a command line, in this way it can be integrated in an automatic delivery process. These scripts export data concerning roles, permissions and permissions sets but doesn’t export data concerning users (passwords, roles assigned…). The data is then imported into the test repository in order to be validated by the team doing the test and the quality control.
• When the test repository is validated the data can be imported into the production repository.
The development team can keep modifying the development repository without modifying the test repository of the quality control team until the next delivery.
Another feature enables the cohabitation of several versions of the same application within the same repository. It is called Permission versioning system. It allows a progressive deployment of the new application and its repository. Users can access both existing and new permission repository, depending on their version of the application.
Application life-cycle management
Posted by z Jean-jacques Jouanneaux on 23 August 2010 06:12 PM
How can the new version of an application be managed with Visual Guard .Net? Is there a migration process integrated (export/import)?