Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / Interop / January 2005

Tip: Looking for answers? Try searching our database.

Dynamically Created Licensed Active X controls and Interop

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
talon2112 - 30 Dec 2004 06:48 GMT
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!

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.