Microsoft KB Archive/316334

= FIX: COM Interop marshaler incorrectly matches types between assemblies =

Article ID: 316334

Article Last Modified on 10/5/2005

-

APPLIES TO


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

-



This article was previously published under Q316334



SYMPTOMS
The COM Interop marshaler may match the types from one assembly with the metadata from a different assembly.



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

318836 INFO: How to Obtain the Latest .NET Framework Service Pack

Hotfix
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it 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 P1 that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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 fix should have the following file attributes or later:

  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



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft .NET Framework Service Pack 1.

Additional query words: kbNETFrame100sp1fix

Keywords: kbvs2002sp1sweep kbbug kbfix kbqfe KB316334

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.