Visual Guard Class Library Documentation

Upgrading v3.1 to v3.2

Migrating the WinConsole

To migrate the WinConsole, you have to unsinstall all components of Visual-Guard before you install the new WinConsole.

Migrating the code of your application

Referencing the new version of Visual Guard assemblies

In order to take into account the version 3.1 of the assemblies of Visual Guard, you should remove the references of old version from your project, add the new ones (select the version 3.1.x.x ), then rebuild your project.

Note: If you have more than one version of Visual Guard installed on your computer, Visual Studio can display more than one version of the assemblies in the list. You should select the version 3.1 of Visual Guard 

If the version 3.1 of Visual Guard assemblies does not appear in the list of .Net assemblies, select the Browse tab in the Add Reference dialog box then select them in the directory <Visual Guard Installation Directory>\Bin. By default the Visual Guard installation directory is C:\Program Files\Novalys\Visual Guard 3.2

Compatible Version of Visual Guard Console

If you decide to integrate the version 3.2 of the Visual Guard runtime in your application, you will need to use the version 3.2 of Visual Guard console to edit security actions of  the application. You cannot use an older version of Visual Guard console to edit actions but you can use it to manage the other items (users, roles, permissions) of a repository.

After modifying security actions for an application integrating the version 3.2 of the runtime with the version 3.2 of the console, these actions will never be compatible with older version of runtime. They will throw exception at runtime if they are executed by an older version of runtime.

See Also

Upgrading v3.0 to v3.1