When you try to serialize a custom data type in an application that is built on the Microsoft .NET Framework 2.0, you receive an exception error message that resembles the following:
Unable to generate a temporary class (result=1).
error CS0200: Property or indexer 'XmlSerializationIssueKB928365.SampleData.Name ListSpecified' cannot be assigned to -- it is read only
Error Stack:
at System.Xml.Serialization.Compiler.Compile(Assembly parent, String ns, XmlS erializerCompilerParameters xmlParameters, Evidence evidence)
at System.Xml.Serialization.TempAssembly.GenerateAssembly(XmlMapping[] xmlMap pings, Type[] types, String defaultNamespace, Evidence evidence, XmlSerializerCompilerParameters parameters, Assembly assembly, Hashtable assemblies)
at System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings, Type [] types, String defaultNamespace, String location, Evidence evidence)
at System.Xml.Serialization.XmlSerializer.GenerateTempAssembly(XmlMapping xml Mapping, Type type, String defaultNamespace)
at System.Xml.Serialization.XmlSerializer..ctor(Type type, String defaultName space)
at System.Xml.Serialization.XmlSerializer..ctor(Type type)
at XmlSerializationIssueKB928365.SampleData.GetXml() in C:\Documents and Settings\User_name\My Documents\Visual Studio 2005\Projects\XmlSerializationIssueKB928365\Startup.vb:line 35
at XmlSerializationIssueKB928365.Startup.Main() in C:\Documents and Settings \User_name\My Documents\Visual Studio 2005\Projects\XmlSerializationIssueKB928365\Startup.vb:line 58
This problem occurs after you install the MS07-040 update.
This issue occurs because the
*Specified property is set to read-only when the custom type defines the
*Specified property for a serialized property.
Note The
*Specified property is a feature in the
XmlSerializer class that controls how a property is generated in XML.
Hotfix 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.
Prerequisites
You must have the .NET Framework 2.0 installed to apply this hotfix.
Restart requirement
You do not have to restart the 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.
Collapse this tableExpand this table
| File name | File version | File size | Date | Time | Platform |
|---|
| System.xml.dll | 2.0.50727.919 | 2,027,520 | 13-8-2007 | 19:35 | x86 |
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the
*Specified property feature, visit the following Web site:
For more information about MS07-040, click the following article number to view the article in the Microsoft Knowledge Base:
931212Â
(http://kbalertz.com/Feedback.aspx?kbNumber=931212/
)
Vulnerabilities in the .NET Framework could allow remote code execution
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684Â
(http://kbalertz.com/Feedback.aspx?kbNumber=824684/
)
Description of the standard terminology that is used to describe Microsoft software updates