License key and CLSID vs. versions and builds

[divspirit]

Hi there,

We are using PDF X-Change Viewer ActiveX in a web page using JavaScript.

Currently we have a license key for version 2.5.207 which is distributed in production. We want to upgrade to 2.5.311 but the license key does not appear to work for this new build. Now we have received a new license key that works for 2.5.311, and also for 2.5.207.

Questions:
1. How does the CLSID of the ActiveX relate to the version or build? Will it be different for different major or minor versions or even builds? Or will it remain the same?

2. How does the license key relate to the version or build? Do we require a new key for each new build, or for each new minor or major version? Does a license key only support builds <=N (i.e. a key for 311 also works for 207)? Does this also hold for major or minor versions?

This information will be really helpful for us in order to plan release cycles of our product.

Thanks!

[Tracker Supp-Stefan]

Hello divspirit,

I can't comment on the CLSID, but yes - a newly released key will work for older builds, and from time to time we will have to issue you a new key - that will still be backwards compatible.
We do not make the changes that require key updates very often but do them from time to time. Your current license key should be valid for at least a few upcoming builds more.

Regards,
Stefan

[divspirit]

Hi Stefan,

Thanks for the info.

Is there someone that can comment on the CLSID?

Regards, Tom

[Lzcat - Tracker Supp]

Hello divspirit
We do not change CLSID each build, so it should be same.
HTH

[divspirit]

Okay, thanks! Then we have enough information for now.

Regards, Tom.

[Tracker Supp-Stefan]