Infralution Support

[ancientOne]

As I become more familiar with the ILS system and available methods for persistence of license data strings, the choices appear to be ILS-provided methods for registry or file storage, and the option of maintaining string data within our own databases.

I am currently persisting license data as string in our own database, but would like to utilize the standard ILS AuthenticatedLicenseInstallForm as a mechanism for user management of installed licenses for such things as license uninstall and file backup.

However, it appears that the ILS AuthenticatedLicenseInstallForm appears to be more oriented to working with license files (_licensefile) as a persistence mechanism.

Am I missing the interface between string-persisted license data and this dialog, or do I need to create temporary license files from my strings in order to work with this dialog? Or would you reccommend a different approach? Thanks.

[Infralution]

If you want to handle persisting the license yourself then you should derive a new class from AuthenticatedLicenseProvider and override the WriteLicense(licenseFile, license) method and the ReadLicense(licenseFile) methods. You can either ignore the licenseFile string parameter or use it (for instance if you needed to store multiple licenses in the database you could use it to identify the license).

Then you before you display the AuthenticatedLicenseInstallForm you should set the LicenseProvider property to an instance of your derived class (alternatively you can override the AuthenticatedLicenseInstallForm.GetLicenseProvider method).
_________________
Infralution Support

[ancientOne]

Thank you.