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 / May 2006

Tip: Looking for answers? Try searching our database.

Problems creating v2.0 Interop for third party product

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Dick - 28 Apr 2006 10:59 GMT
I'm trying to create a v2.0 interop for a third party product. We managed to
do this achieve this with v1.1 and have been using it succesfully for a few
years now. But with v2.0 TlbImp gives the following messages (I've included
them all but I guess the last couple are the important ones). Thanks.

TlbImp : warning TI0000 : Type library importer encountered a property
getter 'UserTrackingEnabled' on type 'AbsDB.AbsOpsSession' without a valid
return type.
The importer will attempt to import this property as a method instead.
TlbImp : warning TI0000 : Type library importer has encountered a source
interface containing properties: 'AbsStringsA'.
TlbImp : warning TI0000 : Type library importer encountered a source
interface on coclass 'AbsUtilThunkMap' with a NewEnum member.  This is not
supported.
TlbImp : warning TI0000 : Type 'AbsUtilThunkMap' is invalid and may only be
partially converted.
TlbImp : error TI0000 : System.SystemException - The type library importer
encountered an error during type verification. Try importing without class
members. : System.TypeLoadException - Missing definition for required runtime
implemented delegate method.
Christian Fröschlin - 28 Apr 2006 13:41 GMT
> I'm trying to create a v2.0 interop for a third party product. We managed to
> do this achieve this with v1.1 and have been using it succesfully for a few
> years now. But with v2.0 TlbImp gives the following messages (I've included
> them all but I guess the last couple are the important ones). Thanks.

I had a similar problem - it seems that the tlbimp 2.0 is stricter
regarding the allowed COM constructs. However, using a tlbimp 1.1
generated wrapper for 2.0 applications worked just fine.

Of course, you might also contact the 3rd party vendor.
Dick - 28 Apr 2006 14:52 GMT
Thanks Christian and yes, since posting, I too have found that our ealier
v1.1 interop (appears to) work just fine. And the answer from the third
party... an expensive upgrade!

> > I'm trying to create a v2.0 interop for a third party product. We managed to
> > do this achieve this with v1.1 and have been using it succesfully for a few
[quoted text clipped - 6 lines]
>
> Of course, you might also contact the 3rd party vendor.
"Peter Huang" [MSFT] - 01 May 2006 03:25 GMT
Hi Richard,

I agree with Dick's suggestion.
I think you may try to use 1.1 interop assembly for now.
If you still have any concern, please feel free to post here.

Best regards,

Peter Huang

Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

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.