.NET XML KB Articles
INFO
HTTP GET and HTTP POST Are Disabled by Default
KB: 819267 |
This article discusses changes in the .NET Framework 1.1 that affect the HTTP GET method and the HTTP POST method on a Web server. This article also describes workarounds for this new functionality.
The .NET-connected Web services support HTTP GET, HTTP POST and SOAP protocols. By default, in .NET Framework 1.0, all three protocols are enabled. By default, in .NET Framework 1.1, HTTP GET and HTTP POST are both disabled. This is for security reasons.
Applications that use HTTP GET or HTTP POST to invoke a Web service fail when the Web service is upgraded to .NET Framework 1.1. These applications receive a
System.Net.WebException
error message that indicates the request format is unrecognized.
Note that the HTML-based test form uses HTTP POST, and therefore the HTML-based test form does not work in .NET Framework 1.1. This is true except on localhost as noted below.
The .NET Framework 1.1 defines a new protocol that is named HttpPostLocalhost. By default, this new protocol is enabled. This protocol permits invoking Web services that use HTTP POST requests from applications on the same computer. This is true provided the POST URL uses http://localhost, not http://hostname. This permits Web service developers to use the HTML-based test form to invoke the Web service from the same computer where the Web service resides.
When you try to access the Web service from a remote computer you do not see the Invoke button. And, you receive the following error message:
The test form is only available for requests from the local machine
 |
Support WebCast: Microsoft .NET Framework Version 1.1: New Features and Changes in System.Data and System.Xml Namespaces
KB: 816892 |
|
The objective of this session is to introduce ADO.NET and XML developers to the new features and changes in the System.Data and the System.Xml namespaces in version 1.1 of the Microsoft .NET Framework.
|
Techniques to Improve Performance of XSL Transformations
KB: 815124 |
|
This article lists some techniques to improve the performance of Extensible Stylesheet Language (XSL) Transformations. XSL is a functional language. XSL does not support features of common language. For example, XSL does not support return values, or globals. XSL is not an object-oriented language, and being modular costs processor cycles. There is no debug available for XSL, therefore, the debugging becomes difficult.
|
Use of MSXML is Not Supported in .NET Applications
KB: 815112 |
Microsoft does not support the use of MSXML (Microsoft’s COM-based XML parser) in .NET applications.
MSXML uses threading models and garbage collection mechanisms that are not compatible with the .NET Framework. Using MSXML in .NET applications through COM interoperability can result in unexpected and problems that are difficult to debug. Microsoft does not recommend or support directly instantiating and using MSXML objects in .NET code, nor does Microsoft recommend or support marshalling MSXML interface pointers across the interop boundary.
|
Interoperability of the .NET SignedXml Class with IBM XML Security Suite
KB: 331370 |
The .NET SignedXml class provides a wrapper around the core XML signature object to make it easier to create and verify XML signatures. Applications that use SignedXml and that interoperate with the Java classes in IBM's XML Security Suite, must interoperate correctly.
This article describes the key issues that you must consider when using SignedXml in these situations.
|
Performance of XSLT Transformations in the .NET Framework
KB: 325689 |
|
This article contains information about the causes of and solutions or workarounds for known performance problems that you might experience when you use the .NET Framework XSLT processor to execute XSLT transformations.
|
SQLXML Managed Classes
KB: 322328 |
|
To read a white paper that discusses how to use SQLXML Managed Classes for .NET code to retrieve XML from a Microsoft SQL Server database or to generate XML on the client side, by using queries, stored procedures, annotated schemas with XPath, or XML templates, please visit the following Microsoft Web site: SQLXML Managed Classes.
|
Webservicessamples.exe Contains ASP.NET Web Services Samples
KB: 320438 |
|
Webservicessamples.exe is a self-extracting executable file that contains a series of samples that demonstrate the features of Microsoft ASP.NET Web services.
|
Clarification: XmlResolver.Credentials Property Documentation
KB: 317492 |
XmlResolver resolves external XML resources, such as entities, DTDs, and schemas. It also processes include and import elements in Extensible Stylesheet Language (XSL) stylesheets or XML Schema Definition language (XSD) schemas. One security risk of using default credentials is that if the Simple Object Access Protocol (SOAP) message is processed by a computer inside a network that is protected by a firewall, the HTTP request that is generated for the external reference may be able to access computers that are not accessible from outside the firewall. These requests may also access ports other than port 80, which may expose even more risk.
The XmlResolver.Credentials Property MSDN documentation states the following:
If credentials are needed but not supplied, the resolver uses default credentials (CredentialCache.DefaultCredentials).
The following statement should be added:
To avoid malicious requests to protected Web sites, do not use DefaultCredentials. Use the credentials set by user.
|
Roadmap for Programming XML with the Pull-Model Parser in the .NET Framework
KB: 313816 |
|
This article provides a roadmap for programming XML with the pull-model parser of the .NET Framework. To help with learning a Microsoft product or technology, roadmap articles provide links to useful information, including online documentation, Microsoft Knowledge Base articles, and white papers.
|
Roadmap for XML in the .NET Framework
KB: 313651 |
This article provides a roadmap to learn about programming in the Microsoft .NET Framework with core Extensible Markup Language (XML) base classes. This article assumes that you are familiar with XML standards, the .NET Framework architecture, and basic .NET application development.
Roadmap articles provide links to useful information, including online documentation, Microsoft Knowledge Base articles, and Microsoft white papers, to help you learn about a Microsoft product or technology.
|
ASP.NET Configuration Overview
KB: 307626 |
|
In contrast to Active Server Pages (ASP) application settings that are stored in the Microsoft Internet Information Server (IIS) metabase, ASP.NET configuration settings are stored in Extensible Markup Language (XML) files.
|
XML Web Services and Apartment Objects
KB: 303375 |
This article describes how to call Apartment objects from XML Web services through the COM interoperability layer. The following are supported methods for calling Apartment objects from XML Web services:
- The Web service can call an Apartment object, such as Visual Basic 6.0, that is registered in a COM+ library application. The COM+ library application must be marked "Requires Synchronization" and must reside on a computer that is running Microsoft Windows 2000 Service Pack 2 or later.
- The Web service can call an Apartment object that is registered in a COM+ server application that resides on a computer that is running Windows 2000 Service Pack 2 or later.
|
|
|
