Article ID: 970510 - Last Review: June 19, 2009 - Revision: 3.0 FIX: A TypeLoadException exception occurs when you run a .NET Framework 3.5 SP1-based applicationSYMPTOMSWhen you run a managed application on a computer that has the .NET Framework 3.5 Service Pack 1 (SP1) installed, a TypeLoadException exception occurs and then you receive an error message that resembles the following:
Could not load type ‘type name’' from assembly ‘assembly name, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=null'. This problem occurs when the application loads a specific generic type. Consider the following sample code: In this situation, this problem occurs when the application loads class C. Note This problem does not occur on earlier versions of the .NET Framework. RESOLUTIONA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix. To download this hotfix from the MSDN Code Gallery, visit the following Microsoft Web site: http://code.msdn.microsoft.com/KB970510
(http://code.msdn.microsoft.com/KB970510)
Note The MSDN Code Gallery displays the languages for which the hotfix is available. If you do not see your language listed, it is because the Code Gallery resource page is not available for that language. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
You can also download this hotfix from the following Microsoft Connect Web site:https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=19242
(https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=19242)
PrerequisitesYou must have .NET Framework 2.0 Service Pack 2 (SP2) or .NET Framework 3.5 Service Pack 1 (SP1) installed on Windows Server 2000, Windows Server 2003 and Windows XP.Restart requirementYou do not have to restart the computer after you install the hotfix if no instance of the Microsoft .NET Framework is running.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe 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.x86-based version for Windows 2000, Windows Server 2003 and Windows XPCollapse this table
x64-based version for Windows 2000, Windows Server 2003 and Windows XPCollapse this table
Itanium-based version for Windows 2000, Windows Server 2003 and Windows XPCollapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
| Article Translations
|
Back to the top
