THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 17/04/2009 at 09:18, xxxxxxxx wrote:
BTW, there are basically two different ways to implement license key validation in Cinema 4D...
1. Using the SNHookClass (which is what's described above) and...
2. Using some combination of Read-/WritePluginInfo() (in stand-alone mode) and Read-/WriteRegInfo() when in License Server mode.
...the first method uses the "Personalize" dialog for your plugin's license key entry in stand-alone mode and lets your plugin's license keys be served by the License Server along with everything else (the user just pastes the appropriate multi-license key(s) you sell them into the License Server dialog).
I haven't used the second method myself, but as far as I can tell, this would be a more brute-force and/or more loosely connected method of doing it. ie. this method stores all licenses locally (on each machine), so the (each) user would have to enter a license key on each machine.
If that's indeed the case, then you'll also be limiting the user to a single "serial package" unless you implement some method of storing/validating multiple 'potential' license keys (using the first method, they can register multiple license keys - one for each "serial package" - with the License Server and the server sends your plugin the one that matches the package in use).
Again, if you're not familiar with the License Server, you should go watch those videos on Cineversity to see how it is (can be) used. A large company could potentially have multiple different serial packages set up, for different departments or laptops vs workstations or... whatever.