HOW TO: Set the JavaScript license for the client side of a web application

Since March of 2019, our licensing mechanism for JavaScript applications has changed to require two files instead of one. If you have downloaded the SDK since that time, you may find that you still experience the nag message when the app is first launched. This can be fixed quite easily without any additional code required!

To do this, create a folder named "LEADTOOLS" and place it in the folder that is being hosted by IIS. Then, simply move your JavaScript licenses there named "LEADTOOLS.lic.txt" and "LEADTOOLS.lic.key.txt". You may have to enable file extension visibility under the View file menu. (See images below). Note that the license files you may have that do not end in .txt are for server and desktop applications.





Troubleshooting:
If you run into problems with this, check that

1. The license files that you are using are JavaScript licenses. The original filenames as sent by our sales team end in ".txt". You can also open the ".lic.txt" file in notepad and the random unlock string at the end of the file should be wrapped in a "[JSLicense]" tag.
   
2. The JavaScript scripts that you are including with your project (The ones in the "Scripts" folder in the above screenshot) are from a post-March version 20 download and not the older installation that uses a single file license mechanism