|
-
Feb 22nd, 2003, 01:49 PM
#1
Thread Starter
Addicted Member
The ActiveX control could not be instantiated because it requires design-time license
I'm using Visual Studio .NET (7.0) and writing an MFC dialog application that requires the use of Microsoft's statusbar control. When I try ot place the statusbar on the dialog serface, I get this error:
The ActiveX control "Microsoft Status Control, version 5.0(SP2)" could not be instantiated because it requires design-time license.
What is a "design-time license" and where do I get\activate it?
Thanks!
Phil
-
Feb 22nd, 2003, 02:51 PM
#2
Junior Member
Reply
Hi,
Try
Here
Design-time licensing is verified by control containers such as Microsoft Visual Basic®, Microsoft Access, or Microsoft Visual InterDev®. Before these containers allow a developer to place a control on a form or Web page, they first verify that the control is licensed by the developer or content creator. These containers verify that a control is licensed by calling certain functions in the control: If the license is verified, the developer can add it.
-
Feb 22nd, 2003, 05:21 PM
#3
Thread Starter
Addicted Member
Thanks for the link. I read the "official" document a few times and am still left a little dumbstruck.
They gave some example MFC code for adding "design-time licensing" to custom developed activex code, but shouldn't the SBarCtrl already be licensed for use?
I still don't understand what I could do to visual studio to "pass" the license check for this control 
Any more advice?
Thanks
Phil
-
Feb 22nd, 2003, 05:29 PM
#4
Thread Starter
Addicted Member
BTW, this occurs with ANY other control as well EXCEPT for the "Default" controls in the toolbox. MSCOMM, Grid controls, etc
-
Feb 26th, 2003, 02:30 AM
#5
Thread Starter
Addicted Member
Anybody have a guess about this? I can't seem to come up with any solution. All I want to do is place a friggin statusbar object on my dialog!
Still scratching my head!
Phil
-
Feb 26th, 2003, 02:51 AM
#6
Thread Starter
Addicted Member
Solution found
for anybody searching for a solution to this problem in the future. Here is the answer:
1) This problem will only exist for computers that have Visual Studio .NET installed, but have never had v6.0 installed.
2) The problem exists becase microsoft considers several of these controls as vb6 controls even though they are commonly used. Microsoft does not add the licensing information to the registry for "vb6 controls".
Solution:
On the visual studio .NET CD, run /Extras/VB6 Controls/vb6controls.reg
That adds all the necessary stuff to the reg. This affects about 20 different "standard" controls.
Phil
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|