licensing a third party control

[sonu]

Hi all,

I have posted this topic previously but still not able to find out any
solution for this probelm.
The scenario is like I am using a third party activeX Control in my
project.

I have registered its ocx using regsvr command. But the main issue is
when I am running the application it is displaying the evaluation
dialog message for the control.
How could I avoid this. I have seen onr article titled in MSDN
"How to dynamically add ActiveX controls that require run-time licenses
in Visual Basic .NET or in Visual Basic 2005"

but this solution is not solving my problem.

I have a valid key to use this control.

Any help will do.

Thanks in adavnce.

 

[VJ]

Talk to the people who provided the control, there might be a bug with the
product. I have had this kind of thing happen more than once, where the
control was still looking up the trial version, even after I activated teh
full version, after I spoke to the company they made me go through a few
manual steps and all was fine

Vijay

 

[gene kelley]

Hi all,

I have posted this topic previously but still not able to find out any
solution for this probelm.
The scenario is like I am using a third party activeX Control in my
project.

I have registered its ocx using regsvr command. But the main issue is
when I am running the application it is displaying the evaluation
dialog message for the control.
How could I avoid this. I have seen onr article titled in MSDN
"How to dynamically add ActiveX controls that require run-time licenses
in Visual Basic .NET or in Visual Basic 2005"

but this solution is not solving my problem.

I have a valid key to use this control.

Any help will do.

Thanks in adavnce.

Regsvr generally has nothing to do with product activation. If you
have a valid key, it needs to be entered somewhere according to the
vendors registration instructions - which vary widely from vendor to
vendor.

I don't know the particulars of your situation, or what you have
tried, but here are a couple of case from my experiences that may or
may not be relevant:

In one case, entering an invalid or mistyped key raises no errors or
warnings. The control simply continues to run in evaluation mode.

If you open a new project and drop the "registered" control on the
form and run, does it run without the nag? If no, then there is a
problem with the registration. If yes, then were you originally using
the evaluation version in the current project an then registered the
control afterwards? I had this situation with a paricular control. It
turned out that this particular control needed to be removed from the
project and then added back after registration. This control
apparently writes a line in the designer when the control is added
indicating whether the control is or is not registered.

In one rare case some time ago, the registration key was upgrade
version specific. An free upgrade to a newer build required a new key
from the vendor.

Gene