And a second question:Is there any way to delete key on an offline machine without deactivation request?
Suppose a client entered a key, that has limit of deactivations, but something happens and the client need to enter another key. The client has hit the limit of deactivations and the key needs to be deleted before CheckAndSaveKey() is called. So if the limit of deactivations has been hit, Deactivate(1) won't succeed hence CheckAndSaveKey() wont either. My question is:
How to delete a product key, which limit of deactivations has already been hit?
And a second question:Is there any way to delete key on an offline machine without deactivation request?
Is there any way to delete key on an offline machine without deactivation request?
No, you need to use a deactivation request. Why would you want to do it otherwise? Why would a customer have an activated machine and then want to activate with a different product key? I can't see a real-world use for this.
but something happens and the client need to enter another key
What's that "something"? There really isn't a real-world use for a customer getting a new key to be activated on the exact same machine.
How to delete a product key, which limit of deactivations has already been hit?
They contact you and tell you increase the deactivation limit. But again, I can't see a real-world situation when this would happen.
Well let's say that a key expires one year after the user have entered it. The user goes to our automatic site and purchares a new key.He wants to enter it in our applicationl, but the old key need to be deleted from the system in order CheckAndSave() to be called for the new one.(because CheckAndSave does not work i f the old key is not deleted).This can happen if the user tries to generate ActivationRequest too.
In that case you would use the exact same product key and change the custom license field (on your order form) when the customer buys an extension. See: http://wyday.com/limelm/help/license-features/#change
So, again, it would be the same key. No deactivation needed. No new product key needed.