.NET XML KB Articles
PRB
Slow XSLT Performance with Managed Parser
KB: 324478 |
|
Extensible Stylesheet Language Transformations (XSLT) style sheets that use the element may experience slow performance when they are used to transform XML data in .NET applications. You may notice this behavior with large XML data, typically in megabytes.
|
XmlValidatingReader Performs Incorrect Attribute and Text Nodes Normalization with Character Entities 0xA and 0xD
KB: 322844 |
With the .NET Framework Service Pack 1 (SP1) release, XmlValidatingReader (System.Xml namespace) performs incorrect attribute or text nodes normalization when the nodes contain character references to the new line characters 0xA and 0xD.
XmlTextReader (and, therefore, XmlValidatingReader) normalizes the attribute value after it is read and all character references and entities are expanded. Because of this, the normalization cannot distinguish between a character reference and the character itself. This also causes incorrect attribute and text normalization.
These problems cause an XML digital signature that is not valid to be generated with the XmlDsigC14NTransform Microsoft .NET Framework class. When you use the XmlDsigC14NTransform class, you see incorrect attribute normalizations.
|
Dynamic Discovery Files Behave Differently When Located in Different Directories
KB: 320607 |
You may notice that Dynamic Discovery files may behave differently when these files are located in different directories. This problem occurs when you use MACHINE as a user account for processModel in the Machine.config file. For example, if you run Disco.exe on Default.vsdisco that is located the in Web root directory, you may receive the following error message:
Access is denied
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Runtime.InteropServices.COMException: Access is denied
|
Limitations for DataSet Schema Files (XSD)
KB: 319372 |
|
You may experience some limitations when you use a DataSet object to read a schema file that the DataSet object did not create.
|
XSL Transformations with XmlDataDocument May Perform More Slowly Than XPathDocument
KB: 318580 |
XSL transformations (XSLT) with System.Xml.XmlDataDocument may run more slowly than XSLT with XPathDocument or XmlDocument.
XmlDataDocument is primarily designed to act as the bridge between the DataSet and XML.
|
You Receive XmlTextReader Error Message When Colon Appears in Processing Instruction
KB: 318351 |
If you use the XmlTextReader to read an Extensible Markup Language (XML) document, and the document contains a processing instruction with a colon, you may receive the following error message:
'xml:stylesheet' is an invalid name for a processing instruction. Line 1, position 3.
|
Error on .NET Client that Consumes a Web Service Through an HTTP Proxy Server
KB: 318140 |
When you use a .NET client to consume a Web service through an HTTP proxy server, you may receive the following error message:
The underlying connection was closed: The remote name could not be resolved.
An HTTP proxy server exists between the Web service and the .NET client, and the proper proxy settings have not been configured.
To resolve this problem, supply the proper proxy configuration settings to the .NET client.
|
You Are Prompted to Check Out a Large XSD File When You Try to View the XML Source
KB: 318082 |
|
When you try to view the extensible markup language (XML) source for a large XML Schema definition language (XSD) file, and if the solution is under source code control, you are prompted to check out the XSD file. Visual Studio .NET must check out the file to save information that must be written to the XSD file.
|
Letter "i" Problems When You Use XML Encoding with Turkish Settings
KB: 317505 |
If the header of an Extensible Markup Language (XML) file specifies an encoding type that contains a lowercase "i," and if you are running a Turkish version of Microsoft Windows, you receive the following error message when you try to read the XML into a DataSet object:
An unhandled exception of type 'System.Xml.XmlException' occurred in system.xml.dll
Additional information: System error.
If you catch this exception in a try...catch block, you receive information that is similar to the following:
The system does not support 'ascXX' encoding. Line 1, position 31. Press any key to continue
When the Microsoft .NET Framework parses the XML file, the encoding type in the header is converted to uppercase before the header is processed. This problem occurs because the Turkish alphabet has two distinct letters that resemble a dotted letter "i" and an undotted letter "i." Windows treats the English lowercase letter "i" as a different Turkish letter than the English uppercase letter "I."
|
DataGrid Is Empty When You Bind DataGrid to a DataSet That Is Returned from a Web Service
KB: 317427 |
The DataGrid control may not contain data under the following circumstances:
You bind a DataGrid control to an ADO.NET DataSet object by using the Form designer, and the designer creates an instance of a DataSet on the form.
-and-
You set that instance variable to a DataSet that a Web method returns through a Web service in the Load event handler.
This problem occurs because the DataGrid control is still bound to the old instance of the DataSet on the form, not the new instance that the Web service returns.
|
Read-Only and Write-Only Class Properties Not Accessible from a Web Service
KB: 317270 |
|
When you try to access read-only and write-only properties of a class that you obtain from a Web service, you cannot view the properties. XML serialization and ASP.NET Web services do not support read-only and write-only properties. Information about these properties is not published in Web Services Description Language (WSDL) documentation.
|
Cannot Unload Assemblies That You Create and Load by Using Script in XSLT
KB: 316775 |
When you use the <msxsl:script> element repeatedly with System.Xml.Xslt framework, a memory leak may occur with a high volume Extensible Markup Language (XML) or Extensible Stylesheet Language (XSL) application.
The classes of the System.Xml namespace support the use of embedded scripting by using the script element in XSL Transformation (XSLT) applications. Therefore, the <msxsl:script> element allows you to choose the programming language (such as Microsoft Visual C# .NET or Microsoft Visual Basic .NET) to perform certain tasks.
Declared functions are contained within script blocks. When you use embedded script with an XSL file, an assembly that contains Microsoft Intermediate Language (MSIL) is created and loaded into memory. Because of a design limitation in this version of the Microsoft .NET Framework, you cannot unload that assembly from memory. This may lead to a memory leak if assemblies are created and loaded repeatedly or in a loop.
|
Element May Cause Data View to Generate an Error Message
KB: 316687 |
When you view an XML document with Data View in the Microsoft Visual Studio .NET integrated development environment (IDE), you may receive the following error message:
Although this XML document is well formed, it contains structure that Data View cannot display. The grid cannot show the data correctly because of the unsupported character "." in element name(s).
|
Read-Only Properties Cannot Be Exposed by XML Web Services
KB: 313584 |
|
If a Web service contains a Web method that either accepts a parameter or returns a value that is an object reference, and the class definition of the object contains a read-only property, the read-only property is not available when you build a proxy assembly for the Web service.
|
Clear() Method Throws an Exception When DataSet Is Bound to XmlDataDocument
KB: 307511 |
The "DataSet.Clear Method" topic in the Microsoft .NET Framework Class Library documentation specifies that the DataSet.Clear method "clears the DataSet of any data by removing all rows in all tables."
However, when a DataSet object is bound to an XmlDataDocument object, an exception is thrown if you call the Clear method on the tables.
For example, if you use the following code: DataSet ds = new DataSet();
//Skip. Populate the DataSet.
// ...
//Bind the DataSet with XmlDataDocument.
XmlDataDocument docCust = new XmlDataDocument(ds);
ds.Tables.Clear();
the Clear method call raises the following exception: System.InvalidOperationException: Cannot add or remove tables from the DataSet once the DataSet is mapped to a loaded XML document.
|
|
|
