View previous topic :: View next topic |
Author |
Message |
SuperNewbie Guest
|
Posted: Fri Apr 28, 2006 10:01 am Post subject: Some suggestions, please... |
|
|
Hi all,
we are new buyers of ILS.
At the moment, we are developing a collection of controls that will be sold on Internet asap.
Since we have no experience in Licensing techniques, we whould like to ask to the Forum readers and Infralution staff some suggestions and/or impressions about the best policy adoptable for licensing a collection of controls.
Samples are good, but some times is difficult for us to understand the diffeences between licensing an application and licensing one or more controls.
Please, let us know and share your experiences!
Thank you |
|
Back to top |
|
|
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Fri Apr 28, 2006 12:03 pm Post subject: |
|
|
You probably will want to use a single license for all the controls in the library. Take a look at the FAQ Can I license all the controls in a library with one key?"
.
Also have a good look at the sample licensed control. If you have specific issues please ask. _________________ Infralution Support |
|
Back to top |
|
|
SuperNewbie Guest
|
Posted: Fri Apr 28, 2006 1:19 pm Post subject: |
|
|
Thank you. This is a good starting point. Do you have a VB version ready?
I have some further questions:
- We well release a collection of components, and licensing all the controls of the collection with one key is a good idea. But we plan to also distribute some controls of the library as separate product groups (three or four controls per package). In this case we obviously must release a different key for every group of controls. Can you suggest the best licensing policy for this?
- Can you please give a three-words definition for EncryptedLicense class and EncryptedLicenseProvider? What is the difference?
Thank you very much |
|
Back to top |
|
|
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Fri Apr 28, 2006 11:14 pm Post subject: |
|
|
You have two options:
1. Issue a separate key (using a different password) for each group of controls that you sell. In this case you will need a separate derived EncryptedLicenseProvider class (as per the FAQ) for each group. This is probably easiest for you - but means your customer has to deal with multiple keys if they buy multiple packages/groups.
2. Use a common key for all the controls but include information in the ProductInfo of the issued license key about what controls it is valid for. Take a look a the following thread for more information http://www.infralution.com/phpBB2/viewtopic.php?t=393&highlight=productinfo.
The EncryptedLicense class contains the information about a particular license key (once it has been loaded and decrypted) - for instance it's serial number and any ProductInfo you included in the key.
The EncrtypedLicenseProvider class is the class that actually reads and descrypts the license keys. It is derived from the standard system LicenseProvider class which provides the mechanism for licensing controls and components. _________________ Infralution Support |
|
Back to top |
|
|
Guest
|
Posted: Sun Apr 30, 2006 6:49 am Post subject: |
|
|
Thank you for you replies.
Bye |
|
Back to top |
|
|
|