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.
Ties a license to a specific machine so the software cannot be installed on multiple machines without permission.
Indicates that the protected software is still in beta and may not be used after a certain point.
Prompts the user for registration details and unlocks licenses that require a serial number.
Displays a splash screen during validation.
Provides an evaluation period for the protected software.
Prompts the user for a serial number from a previous version of the product.
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.
Resets the client state of an IResettable limit. Typically used with a State limit to reset the temporary grace periods for disconnected machines.
Restricts how much time the user has to use the protected software.
Limits access to specific Types in the assembly.
Restricts how many times the user can run the protected software or how many times they may perform a protected action.
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.
Restricts the use of protected software to machines that have been assigned a specific IP address.
Limits the active number of browser sessions allowed to connect simultaneously to a single ASP.NET application.
Controls the number of running instances of the protected software on a single machine. Use Network Licensing to control instances across the network.
Allows the protected software to execute in a designer such as Visual Studio .NET.
Explicitly marks a license as invalid.
|License Server|| |
Communicates with a license server to remotely monitor and validate the use of the protected software.
Requires that only one of it's child limits is valid.
Restricts the protected software to running on a list of approved operating systems.
Restricts the protected software to use by a specific publisher that has strong named their assemblies.
Prevents the software from being used in an IDE and only allows it to run in a standard runtime host.
Serves as a lite custom limit.
Restricts the types of host applications that can use the protected software.
Verifies the accuracy of the system clock by contacting a remote SNTP server.
Ties a license to a specific release version of the protected software.
Filters child limits based on the type of application currently running.
Restricts certain limits based on the presence of named features or serial number flags.
Determines the connected state of the machine.
Determines if the software is being used over a remote desktop connection.
Validates child limits when the parent limit matches the desired state.
Determines if the software is being used within a virtual machine
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.
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.