RE: XSLT transforms and complex parameter types

From: Kevin Yu [MSFT] (v-kevy_at_online.microsoft.com)
Date: 12/17/04 

Date: Fri, 17 Dec 2004 07:19:47 GMT

Hi Cameron,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that XSLTransform works incorrectly when the
parameter contains node. If there is any misunderstanding, please feel free
to let me know.

Based on my research, this is a known issue in current .net framework.
Since IE uses MSXML to process xml data, it is working properly. This issue
will be fixed in the next version of .net framework. Currently, I think you
have to use MSXML to process with the xsl.

HTH.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

Relevant Pages

  • Re: What should I keep?
    ... .NET Framework 1.1 Hotfix ... I also have the following MSXML listed: ... MSXML 4.0 SP2 ... MSXML 4.0 SP2 Parser & SDK ...
    (microsoft.public.windowsxp.general)
  • Re: What should I keep?
    ... .NET Framework 1.1 Hotfix ... I also have the following MSXML listed: ... MSXML 4.0 SP2 ... MSXML 4.0 SP2 Parser & SDK ...
    (microsoft.public.windowsxp.general)
  • Re: What should I keep?
    ... .NET Framework 1.1 Hotfix ... I also have the following MSXML listed: ... MSXML 4.0 SP2 ... MSXML 4.0 SP2 Parser & SDK ...
    (microsoft.public.windowsxp.general)
  • Re: What should I keep?
    ... .NET Framework 1.1 Hotfix ... I also have the following MSXML listed: ... MSXML 4.0 SP2 ... MSXML 4.0 SP2 Parser & SDK ...
    (microsoft.public.windowsxp.general)
  • Re: XSLT 2 Processors
    ... One reason certainly is that there are various specifications (e.g. XSLT 2.0, XPath 2.0) involved that are still a work in progress. ... Microsoft for instance decided not to ship XSLT/XPath 2.0 or XQuery support in the .NET framework before those standards are a W3C recommendation. ... If you want XSLT 2.0 support in MSXML then look at this post ...
    (comp.text.xml)