Hi Hans,

I understand your point but here is what we did.

Our application was using WebScheduler V3 with the V3 runtime license in the web.config without any problem.

Yesterday, we updated all of our DLLs and replace the license in our web.config by <add key="ISNet.WebUI.WebScheduler.v4_0_1000.RunTimeLicenseKey" value="our V4 runtime key" />

When we go on a page having a webscheduler, there is an unhandle exception: "The ISDataSourceControl used in this application is not licensed". the Web Scheduler is licensed because if we remove the license from the web.config, the page loads but the scheduler does show an unlicensed message.

The workaround we found was to put both V3 and V4 license in the web.config like this:

<add key="ISNet.WebUI.WebScheduler.v4_0_1000.RunTimeLicenseKey" value="our v4 runtime key" />
  <add key="ISNet.WebUI.WebScheduler.v3_0_1000.RunTimeLicenseKey" value="our v3 runtime key" />

It look like WebScheduler is looking for the V4 license but that ISDataSource is looking for the V3.

Regards

Alex

We tried that unofficial build, and it solved our problem.

Thank you.