This article was previously published under Q328560
In an application that was built on the Microsoft .NET Framework version 1.0, when you try to deserialize data that has a value of Byte in a DataSet class, you receive the following error message:
Exception has been thrown by the target of an invocation
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, Microsoft recommends that you wait for the next .NET Framework 1.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.
The English version of this hotfix has the file attributes (or later) 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 tool in Control Panel.
Date Time Version Size File name -------------------------------------------------------------- 13-Sep-2002 05:18 1.0.3705.359 69,632 Corperfmonext.dll 13-Sep-2002 16:59 1.0.3705.359 1,953,792 Mscorlib.dll 13-Sep-2002 05:10 10,256 Mscorlib.ldo 13-Sep-2002 05:17 1.0.3705.359 2,269,184 Mscorsvr.dll 13-Sep-2002 05:18 1.0.3705.359 2,265,088 Mscorwks.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.