FIX: Loader Does Not Check the Accessibility of Interfaces Implemented by a Type

Article translations Article translations
Article ID: 319422 - View products that this article applies to.
This article was previously published under Q319422
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all


Because the Common Language Runtime (CLR) type loader does not properly check the accessibility of all interfaces implemented by a Type, it is possible for a Type to claim to implement an interface that is defined internal to another assembly.


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


This bug was corrected in .NET Framework (2003|1.1). This problem was first corrected in Microsoft .NET Framework Service Pack 1.


Article ID: 319422 - Last Review: October 24, 2013 - Revision: 3.1
  • Microsoft .NET Framework Software Development Kit 1.0 Service Pack 2
  • Microsoft .NET Framework Software Development Kit 1.0 Service Pack 2
kbnosurvey kbarchive kbbug kbfix KB319422

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from