Limits restrict the protected software to a specific set of runtime or designtime conditions. DeployLX includes 35 limits that you can use to control the use of your software.
Activation | Ties a license to a specific machine so the software cannot be installed on multiple machines without permission. |
Beta | Indicates that the protected software is still in beta and may not be used after a certain point. |
Registration | Prompts the user for registration details and unlocks licenses that require a serial number. |
Splash | Displays a splash screen during validation. |
Trial | Provides an evaluation period for the protected software. |
Upgrade | Prompts the user for a serial number from a previous version of the product. |
Feature | The Feature Limit is used to enable or disable named product features. The features can be enabled when generating a serial number, or later with an extension code. |
Reset |
Resets the client state of an IResettable limit. Typically used with a State limit to reset the temporary grace periods for disconnected machines. |
Time | Restricts how much time the user has to use the protected software. |
Type | Limits access to specific Types in the assembly. |
Use | Restricts how many times the user can run the protected software or how many times they may perform a protected action. |
Domain Name | Restricts the use of protected ASP.NET controls and applications to a specific domain name. |
HTML Branded | Injects HTML into the ASP.NET response when the protected software is used. |
IP Address | Restricts the use of protected software to machines that have been assigned a specific IP address. |
Sessions | Limits the active number of browser sessions allowed to connect simultaneously to a single ASP.NET application. |
Application | Controls the number of running instances of the protected software on a single machine. Use Network Licensing to control instances across the network. |
Design Time | Allows the protected software to execute in a designer such as Visual Studio .NET. |
Invalid | Explicitly marks a license as invalid. |
License Server | Communicates with a license server to remotely monitor and validate the use of the protected software. |
Or | Requires that only one of it's child limits is valid. |
OS | Restricts the protected software to running on a list of approved operating systems. |
Publisher | Restricts the protected software to use by a specific publisher that has strong named their assemblies. |
Runtime | Prevents the software from being used in an IDE and only allows it to run in a standard runtime host. |
Script | Serves as a lite custom limit. |
Service | Restricts the types of host applications that can use the protected software. |
TimeServer | Verifies the accuracy of the system clock by contacting a remote SNTP server. |
Version | Ties a license to a specific release version of the protected software. |
Application Type | Filters child limits based on the type of application currently running. |
Feature Filter | Restricts certain limits based on the presence of named features or serial number flags. |
Online | Determines the connected state of the machine. |
Remote Desktop | Determines if the software is being used over a remote desktop connection. |
State | Validates child limits when the parent limit matches the desired state. |
Virtual Machine | Determines if the software is being used within a virtual machine |
Network License | Controls a network service that coordinates shared use of the protected software on a network. |
Network License Client | Requests authorization from a network license service. Network License Client Limit | NetworkLicenseClientLimit Class |
If the built in limits aren't enough you can create custom limits to enforce your own business rules.
See the Custom Limits topic for details.