BUG: PE File Is Unverifiable When You Use PEVerify Tool (315479)
The information in this article applies to:
- Microsoft Visual C# .NET (2002)
- Microsoft Visual C# .NET (2003)
This article was previously published under Q315479 SYMPTOMS When you use the PEVerify tool (Peverify.exe) to determine
whether a portable executable (PE) file and associated metadata meet type
safety requirements, the resulting PE file is unverifiable in some scenarios
(such as those shown in the sample code in the "More Information" section of
this article), even though it does not use any unsafe code. CAUSE The private member X of the class A is accessible only from
member functions and friends of the class A. The issue described in the
"Symptoms" section of this article occurs when you attempt to "spoof" the C#
compiler to circumvent this limitation by tampering with the definition of the
class A, which makes the member X public. Under these circumstances, the C#
compiler ignores the resolution scope and references the inappropriate DLL
file. The code is compiled successfully. The problem occurs only when the code
is verified by the PEVerify tool. STATUSMicrosoft has confirmed that this is a bug in the Microsoft
products that are listed at the beginning of this article.
Modification Type: | Major | Last Reviewed: | 4/11/2003 |
---|
Keywords: | kbbug kbnofix KB315479 |
---|
|