Licensing Instructions

Standard (Royalty-Free) Licensing

When installing by running the setup executable, a license will be activated and installed to the system. No additional steps are needed for distribution.

When installing by a package or archive, visit the URL below to generate a Runtime License value.

https://www.callback.com/full/CTCJA

After obtaining the Runtime License value assign this to the RuntimeLicense property to license the application for deployment. For instance:

component.SetRuntimeLicense("<value from above>")

This provides a license to the component and your application will run without a license prompt on any machine to which it is distributed.

Note that each component instance in your code must be assigned a Runtime License value.

Trial Licensing

When installing by running the setup executable, no other actions are required.

When installing by a package or archive, visit the URL below to generate a 30-day Trial Runtime License value.

https://www.callback.com/trial/CTCJA

After obtaining the Runtime License value assign this to the RuntimeLicense property to license the application for deployment. For instance:

component.SetRuntimeLicense("<value from above>")

This provides a 30-day trial license to the component and your application will run without a license prompt on any machine to which it is distributed during that time.

Note that each component instance in your code must be assigned a Runtime License value.

Deployment

After licensing your application using one of the above methods, no further steps are required to embed the license for distribution. When distributing to other machines, include the executable and the toolkit's .dll, "cbfsvault24.dll".

When using the static library, "cbfsvault24s.lib", the license will be embedded into the application during compilation as will the static library. In this case only the executable needs to be deployed.

License Transfer

If you would like to transfer your license to another system, please complete our license transfer form. This will ensure your installations are not mistaken for license violations.

For additional information about our product activation process, please refer to our product activation FAQ.