WinLicense > License Restrictions

WinLicense accepts different type of restrictions for the generated licenses. You can create licenses with no expiration restrictions at all (so the license will work forever) or add one or more different expiration restrictions to a single license, so your license can expire for example by number of days or by number of executions (the one that happens first)

•Days Expirations: This is the number of days that your license can run since it was initially used. When your customer runs your application with a license with days expiration, WinLicense will keep track of the day that the license was first used. After that, the license will expire after the given number of days. When the license expires by days, WinLicense will signal the event MSG_ID_LICENSE_DAYS_EXPIRED (from the Customized Dialogs panel)

•Date Expiration: You can set a specific expiration date for your license. The license will expire when the expiration date arrives, even if the user has no launched the application before that date. When the license expires by date, WinLicense will signal the event MSG_ID_LICENSE_DATE_EXPIRED (from the Customized Dialogs panel)

•Executions: You can restrict a license to be only used a specific number of times on a machine. Each time that your application is launched, the internal execution counter will add one execution. When there are no more executions left, WinLicense will signal the event MSG_ID_LICENSE_EXECUTIONS_EXPIRED (from the Customized Dialogs panel)

•Runtime: You can restrict your license to be only used a specific amount of minutes in memory. Each time that the application is launched, the runtime expiration starts again from zero till it reaches the specific limit in the license. When your application has been running in memory during the specific runtime limit, WinLicense will signal the event MSG_ID_LICENSE_RUNTIME_EXPIRED (from the Customized Dialogs panel)

•Global Time: You can set the maximum time (minutes) that a license can be used on a machine. For example, if you set 180 minutes as global time expiration, your customer can launch your application multiple times but WinLicense keeps a counter of the number of minutes that your application has been in memory. Once that the customer has been running your application during more than 180 minutes (no matter if he just launched one time and consumed the 180 minutes or it took him 3 months to reach the 180 minutes) your license will be expired. When the global time is expired, WinLicense will signal the event MSG_ID_LICENSE_GLOBALTIME_EXPIRED (from the Customized Dialogs panel)

•Install Before Date: You can force a license to be installed on a machine before a specific date. If your customer installs the license after the specific date, WinLicense will signal the event MSG_ID_LICENSE_INSTALLATION_TIME_EXCEEDED (from the Customized Dialogs panel)

•Country Locking: This option is used to create a restricted license that can only be used in a specific country. Notice that the country is determined by the Windows Language settings and it's not a real proof that the user is really running your application from a specific country. If the current language does not match the specific country inside the license, WinLicense will signal the event MSG_ID_LICENSE_COUNTRY_ERROR (from the Customized Dialogs panel)

•Network Instances: This option is used to limit the number of instances inside a network. Please, refer to the Network Instances (Floating licenses) section for more information.