FIX: Tlbimp.exe cannot handle coclasses that list source interfaces that are defined in a different type library (318466)



The information in this article applies to:

  • Microsoft Visual Studio .NET (2002), Professional Edition

This article was previously published under Q318466

SYMPTOMS

You may receive the following error message:
TlbImp error: System.TypeLoadException - Could not load type Interop.testlib.ISourceInterface from assembly Interop.TestLib, Version=1.0.0.0.
You may receive this error message under the following circumstances:
  • Your type library defines a coclass that lists a source interface.
  • The source interface is defined in a different type library.
  • You use the Type Library Importer (Tlbimp.exe) to create a managed wrapper from the original type library.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for the .NET Framework 1.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

318836 How to obtain the latest .NET Framework 1.0 service pack

Hotfix information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. The English version of this fix should have the following file attributes or later:
   Date         Time      Version      Size     File name     Platform
   -------------------------------------------------------------------
   04-Mar-2002  11:36 AM  1.0.3705.210 1.86 MB  Mscorlib.dll  x86
   01-Mar-2002  11:29 AM  1.0.3705.210 2.15 MB  Mscorwks.dll  x86
   01-Mar-2002  11:29 AM  1.0.3705.210 2.15 MB  Mscorsvr.dll  x86
				

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in the .NET Framework 1.0 Service Pack 2.

Modification Type:MinorLast Reviewed:9/27/2005
Keywords:kbHotfixServer kbQFE kbvs2002sp1sweep kbbug kbfix KB318466