Redistributing the licensed component

[Unregistered]

To Imaging Source,

We are trying to redistribute the text control with our application but we are unable to get the licensing information to be transfered from the development machine to the target machine.

The application is written using Director, but it could be any other scripted programming environment other than VB or C++.

Here's the problem:

At run-time, the application is using CoCreateInstance rather than CoCreateInstanceLic to create an instance of the component. This is code we don't have access to i.e. the director application provides support for ActiveX components but doesn't provide a facility to give a run-time license string (as opposed to VB or C++).

So instead of providing a run-time license, we would like to be able to generate a full machine license at installation time.

We are using the WISE installer, it let's us copy the files to the target system and register the OCXs and DLLs using regsvr32 utility. This also doesn't provide for licensing.

So the real question is:

Is there a way to create on a development machine where the control is correctly registered a license file and then to copy this license file to the target machine and to get your control to find this license file?

Or

Is there a registry key we can set on the target machine to let the control know of its licensing information.

Or

Would you be able to release a new version of the control with an extra write-only property "License" that can be set just after the control is created and that would disable the 'demo' warning message. I have found many components that use this method of licensing when the target development environment doesn't support IClassFactory2 interface.

Failing all this, I would be able to write an ActiveX wrapper around your activeX wrapper with the licensing information burned into my wrapper (or taken from a file or registry) and then distribute both my application, my wrapper and your control to the target machines. I just need your confirmation that it would not be a breach on the licensing agreement for this component?

Thanks


This message was originally posted by Marc Ridey in the old TX Text Control Support Forum.

[Meik Dankleff]

Marc,

the only chance I see would be the extra license property, but I haven't talked about this with a programmer, so I don't know if there are some issues that make such a solution impossible. Anyway, it would take until the next version for this feature to be implmented.

So, at the moment your only choice is a wrapper OCX. As you are not offering a way to use this component in development mode when wrapping the OCX, you won't breach the licensing agreement.


This message was originally posted by Meik Dankleff in the old TX Text Control Support Forum.