How to I perform the license check again if my application never closes/re-launches?

When using Instant Protection PLUS 3, the main license check is performed at application startup. For applications that are rarely closed, this can mean that the licensing will not check the local license file as often, but you can use the Instant Protection PLUS 3 API to check the license file's expiration date or other fields at any time.

When using our DLL interface, we do not recommend making multiple calls to the CallIp/CallipEx function, which is the initial call made when your application first launches. After that, you can make a call to the API functions, such as WR_LFGetDate,

If it is past the expiration date, you can make a call to InfoCheck (a standard web service call that needs the License ID and Activation Password, which you can get using WR_GetLicenseID and WR_LFGetString) to see if the expiration date has been updated.

  • If the expiration date has not been updated, then you could prompt the user that the license has expired, and your application will now close (or whatever logic would be most appropriate, such as a warning first and then closing the app at some point after that). From there, it would use the built-in functionality to validate with SOLO Server and pull a new expiration date if the license has been updated.
  • If the expiration date has been updated, you can update it in the local license file using WR_LFSetDate on Field ID 1.

With our more advanced licensing client, Protection PLUS 5 SDK, you have much more control and can silently make the standard license checks and validations whenever you want.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us