When the license is validated DeployLX determines if the time limit has expired. DeployLX validates the time based on on one of the following types
|At A Time
Tracks usage from the time the application is launched. Use the TimeExpired event to be notified when the time has expired.
|Tracks total amount of running time even between sessions.
|From First Use
|Tracks the amount of time from the date the software was first run.
|Expire the license on a specific date.
Monitor the time expiration by requesting an instance of the TimeMonitor from the license by calling GetTimeMonitor. Then subscribe to the TimeExpired event to receive notification when the time limit has expired.
DeployLX automatically detects attempts to roll back the system clock. If the clock has been rolled back since the last time the license was validated validation fails.
DeployLX makes accommodations for minor clock adjustments from a time server in an enterprise environment and daylight savings.
When the license contains a Time Server Limit then DeployLX will not keep track of when the license was last used and instead will defer to time reported by the server.
During development use the TestDate property to simulate a future date without interfering with the clock-tampering features of DeployLX.
The Time limit supports extensions to authorize continued use of the software past it's expiration. This can be used to create a subscription service that requires periodic renewal or to extend the evaluation period of a trial.
Use the Generate Extension Code form to create codes for extending the time limit on a users machine.
The limit uses DeployLX's Secure Storage service to track state on the client machine. Secure storage imposes additional security requirements that may require additional configuration
See the Secure Storage topic for more details.
The forms may be customized or completely replaced to fit your specific application style.
See the How to Create a Custom Form topic for details on replacing or customizing the form.