FIX: COM Interop marshaler incorrectly matches types between assemblies

This article was previously published under Q316334
This article has been archived. It is offered "as is" and will no longer be updated.
The COM Interop marshaler may match the types from one assembly with the metadata from a different assembly.
To resolve this problem, obtain the latest service pack for the Microsoft .NET Framework. 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


A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.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 item in Control Panel.
   Date         Time   Version        Size     File name      Platform   -------------------------------------------------------------------   30-Jan-2002  9:20   1.0.3705.206   2256896  Mscorwks.dll   x86   30-Jan 2002  9:20   1.0.3705.206   2260992  Mscorsvr.dll   x86				
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 Microsoft .NET Framework Service Pack 1.

Article ID: 316334 - Last Review: 11/02/2013 22:50:00 - Revision: 4.0

Microsoft Visual Studio .NET 2002 Professional Edition, Microsoft .NET Framework 1.0

  • kbnosurvey kbarchive kbvs2002sp1sweep kbbug kbfix kbqfe KB316334