| View previous topic :: View next topic |
| Author |
Message |
ancientOne
Joined: 26 May 2011
Posts: 26
|
 Posted: Tue Nov 08, 2011 6:48 pm Post subject: Licensing of optional features with ILS Version 5 |
 |
|
I recently started the following thread about different approaches to licensing optional features using ILS:
http://www.infralution.com/phpBB2/viewtopic.php?t=2263&sid=297ef377a9d9f73274ca28b08a0fc9c3 and received a good synopsis of available options under ILS Version 4.7. In reviewing the following new features in ILS Version 5:
| Quote: | • Added Authentication Data for authenticated license keys. This enables you to specify string data that is uploaded to the Authentication Server and passed to the application as part of the Authenticated License when the license key is authenticated. The application can access this data via the AuthenticatedLicense.AuthenticationData property. This enables you to pass much larger amounts of information to an application then is possible with ProductInfo without impacting the size of the license key.
• Added Application Data for authenticated license keys. This enables the application to pass back string data to the Authentication Server when a license key is authenticated. This is done by either calling the new AuthenticatedLicenseProvider.AuthenticateKeyWithData method explicitly or by overriding the AuthenticatedLicenseProvider.GetApplicationData method. The Application Data can then be imported and displayed in License Tracker. |
I was wondering if the new feature set of ILS 5 makes better provision for licensing optional features than provided with version 4.7? I am specifically interested in alternatives to provisioning for every different feature combination in order to achieve feature coding via the encrypted ProductInfo property.
Also, how much re-engineering of the currently working ILS 4.7 code will be required? I am using authenticated licensing and have no legacy user base at this point.
Thanks |
|
| Back to top |
|
 |
Infralution
Joined: 28 Feb 2005
Posts: 5027
|
| Posted: Tue Nov 08, 2011 10:26 pm Post subject: |
|
|
Version 5 doesn't really change the fundamentals of the advice given in the other thread. The new AuthenticationData does provide an alternative (to ProductInfo) mechanism for passing information to the application. If your ProductInfo is relatively short (eg a letters representing licensed features) then there is probably no advantage to using AuthenticationData over ProductInfo. Its really designed for cases where you have a large amount of data you want to provide to the app.
The main breaking change between Version 5 and Version 4 is that the names of the assemblies and namespaces have changed (because the Infralution.Licensing assembly is now split into different assemblies for different target platforms eg WPF, Windows Forms, ASP.NET). This typically just requires changing your reference (if you are not including the source code) and changing the Using/Imports statements from Infralution.Licensing to Infralution.Licensing.Forms.
_________________
Infralution Support |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
