I am encoutering a problem when attempting to create Licensed Active X
(VB) controls dynamically. I get a 747 "No design time license
information found..." error.
I have read the KB arcticles on using Licensed Active X controls in c#
interop scenarios, but our situation is a bit different.
We have an Active X control that is hosted by the AXHost. This control
is responsible for creating application specific Active X controls
dynamically. It uses the licenses.Add method when one of these
controls is licensed. This worked greate in VB and we had no problems
(other than not being able to debug unless you had a design time
license).
However, when we attempt this with our new .net application, it fails
miserable with the 747 error mentioned above. Using trace messages, I
have been able to see that the license gets added correctly and that it
is indeed the right license. The Controls.Add fails with the 747
error. The only time we'd see this in our completely Active X solution
was when the license key was in correct. This is not the case here,
but for some reason it's happening.
FWIW, this scenario works fine for non-licensed Active X components.
Anyone have any ideas why this would behave differently in an interop
scenario?
much thanks!
-Scott
talon2112 - 03 Jan 2005 19:36 GMT
I guess no one else has run into an issue like this before?
When doing this under VB6, we got the same error when running in the
debugger, but it worked fine when running a compiled executable.
It seems like the .net framework makes COM interops think they are
running in a debugging setting.
I'm really stuck on this and it's critical for us... if anyone has any
ideas, please drop me a note!
thanks!