In Microsoft .NET Framework 2.0, you migrate a code from the XslCompiledTransform class to the XslTransform class in the namespace of System.Xml.Xsl. The XslTransform.Transform method has an overload method that accepts both the XPathNavigator object and the XmlResolver object as arguments. For example,the XslTransform.Transform method has the following overload method:
public void Transform(XPathNavigator, XsltArgumentList, XmlWriter, XmlResolver)
However, the XslCompiledTransform.Transform method does not have the same overload method. The following is an overload method of the XslCompiledTransform.Transform method which accepts the XmlResolver object:
public void Transform(XmlReader, XsltArgumentList, XmlWriter, XmlResolver)
This overload method uses the document that is specified by the XmlReader object as input.
If you try to produce an XmlReader object from an XPathNavigator object, you have to call the ReadSubtree method. This is not efficient. Additionally, it may be very time-consuming if you handle a large code base.
Hotfix Replacement Information
The hotfix that corresponds to KB968556 has been superseded with the hotfix KB976814, which contains all fixes that were previously included in KB968556. You should use the hotfix KB976814 to fix the issues described in KB968556. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
976814 FIX: A System.InvalidOperationException exception occurs when you use a WCF client proxy that is generated by the ServiceModel Metadata Utility tool from the service metadata that is in the .NET Framework 3.5
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
After you apply this hotfix, the following overload method is accepted in the XslCompiledTransform.Transform method:
public void Transform (XPathNavigable,XsltArgumentList,XmlWriter,XmlResolver)
For more information about the XslTransform.Transform method, visit the following Microsoft Web site: