FIX: When you use the MSIL Assembler in the .NET Framework 2.0 to generate a PE file from the MSIL code, the PE file may close unexpectedly, and you may receive an access violation error message
This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario:
- In the Microsoft .NET Framework 2.0, you use the Microsoft intermediate language (MSIL) Assembler (Ilasm.exe) to assemble the MSIL code.
- You use the MSIL Assembler to generate a portable executable (PE) file from the MSIL code.
- The MSIL Assembler /flags option is set to 3.
- The MSIL code contains more than 32,767 local variables in a single method.
- You run the PE file.
Hotfix informationA 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 .NET Framework 2.0 service pack 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: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.
PrerequisitesThere are no prerequisites for this hotfix.
Restart informationYou do not have to restart the computer after you apply this hotfix.
Registry informationYou do not have to change the registry.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
Hotfix file informationThis hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.
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.
The .NET Framework 2.0 hotfix, 32-bit
|File name||File version||File size||Date||Time||Platform|
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 919514 - Last Review: 12/09/2015 05:49:52 - Revision: 2.0
Microsoft .NET Framework 2.0
- kbnosurvey kbarchive kbbug kbfix kbtshoot kbHotfixServer kbqfe KB919514