FIX: Error message when you use the MSIL Assembler (Ilasm.exe) to compile a Visual Studio project: "Invalid TypeDefID of exported type"

This article has been archived. It is offered "as is" and will no longer be updated.
When you use the Microsoft intermediate language (MSIL) Assembler (Ilasm.exe) in the Microsoft .NET Framework 2.0 to compile a Microsoft Visual Studio project, you may receive an error message that resembles the following: : error -- Invalid TypeDefID of exported typeAssembled method Dll::.ctor

***** FAILURE *****
This problem occurs because two inner classes in the MSIL code have the same name.

Software update information

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 Microsoft .NET Framework 2.0 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.


No prerequisites are required.

Restart requirement

You do not have to restart the computer after you apply this software update.

Software update replacement information

This software update does not replace any other software updates.

File information

The English version of this software update 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 Microsoft .NET Framework 2.0, Itanium Architecture
File nameFile versionFile sizeDateTime
The Microsoft .NET Framework 2.0, x64
File nameFile versionFile sizeDateTime
The Microsoft .NET Framework 2.0, x86
File nameFile versionFile sizeDateTime
More information
After you apply this software update, you must type the full path of a nested class when a multi-module assembly contains double-nested public types. For example, you use code that resembles the following code example before you apply the software update.
.class extern public forwarder Encl{.assembly extern multi_supplier}.class extern public forwarder Nest1{.class extern Encl}.class extern public Nest2{.class extern Nest1}
After you apply the software update, the code must resemble the following code example.
.class extern public forwarder Encl{.assembly extern multi_supplier}.class extern public forwarder Nest1{.class extern Encl}.class extern public Nest2{.class extern Encl/Nest1
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More information
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: 928382 - Last Review: 01/16/2015 04:07:00 - Revision: 3.0

Microsoft .NET Framework 2.0

  • kbnosurvey kbarchive kbbug kbfix kbqfe kbHotfixServer KB928382