Article ID: 896982
Article Last Modified on 3/23/2007
APPLIES TO
- Microsoft .NET Framework 1.1
SYMPTOMS
When you try to run an application that is built on the Microsoft .NET Framework 1.1, a System.TypeLoadException exception occurs. This problem occurs when an array of a user-defined class is created in the application, and the user-defined class does not provide a TypeDefId token.
CAUSE
This problem occurs because a TypeDefId token is not provided for an ExportedType value in the Microsoft intermediate language (MSIL) for the application. For example, consider the following scenario:
The MSIL for the application contains code that resembles the following code example.
.class extern public class1 { .file test.netmodule // .class 0x02000002 // Does not define TypeDefId }Note This code example contains a definition for the class1 class that does not provide a TypeDefId token.
The application contains code that resembles the following code example.
class1 [] b1; b1 = new class1[5];
Note This code example implements an array of class1 objects.
In this scenario, the MSIL definition for the class1 class does not provide a TypeDefId token. Therefore, the .NET Framework 1.1 common language runtime (CLR) throws the exception when you try to run the application.
Note The European Computer Manufacturers Association (ECMA) specification does not require a TypeDefId token to be provided for an ExportedType value.
RESOLUTION
Hotfix information
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 .NET Framework 1.1 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.
Prerequisites
The following list contains prerequisites for the hotfix:
- The .NET Framework 1.1 Service Pack 1 (SP1)
Restart requirement
You do not have to restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
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.
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Mscorlib.dll | 1.1.4322.2323 | 2,138,112 | 06-May-2005 | 22:37 | x86 |
| Mscorlib.ldo | Not Applicable | 10,904 | 06-May-2005 | 22:39 | Not Applicable |
| Mscorsvr.dll | 1.1.4322.2323 | 2,519,040 | 06-May-2005 | 22:48 | x86 |
| Mscorwks.dll | 1.1.4322.2323 | 2,506,752 | 06-May-2005 | 22:49 | x86 |
STATUS
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
Keywords: kbwinserv2003sp2fix kbfix kbhotfixserver kbqfe kbpubtypekc KB896982
