Upgrading v 2018.1 to v 2019

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

In order to take into account the version 2019 of the assemblies of Visual Guard, you should remove the references of old version from your project, add the new ones (select the version 2019), 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 2019 of Visual Guard

If the version 2019 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>\VisualGuardConsole . By default the Visual Guard installation directory is C:\Program Files\Novalys\Visual Guard 2019

VisualGuard 2019 now supports .NetCore applications also along with .NetFramework applications.

Following new assemblies have been introduced in this version to support .NetFramework and .NetCore.

1. Novalys.VisualGuard.Security.Core contains all classes required to support .Net Core applications. You must add this assembly in your application, if you want to integrate Visual Guard in .net core applications.
2. Novalys.VisualGuard.Security.NetFramework contains all classes required to support .Net Framework applications. You must add this assembly in your application, if you want to integrate Visual Guard in .net framework applications.

Caution
You must add either Novalys.VisualGuard.Security.NetFramework or Novalys.VisualGuard.Security.Core to your application. (Depending on type of application's framework)

If you decide to integrate the version 2019 of the Visual Guard runtime in your application, you will need to use the version 2019 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 2019 of the runtime with the version 2018 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.

Other Resources