469,592 Members | 2,046 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,592 developers. It's quick & easy.

System.XML vs MSXML 3/4

I am current in the process of converting an existing ASP application to
ASP.NET. The existing application makes extensive use of server side XML
transformations as in rslt=myxmlobj.tranform(myxsltdoc).

Now I have included the reference to the MSXML 3.0 object into my .NET
application and have it working but I am wondering am I better off using the
System.XML object that comes naturally with .NET. Is there a performance
gain? Is it safer for rollout to an ISP? Is it safer to place a
System.xml.xsl.transform object into the application cache versus a
MSXML.DOMDocument30.

Thanks in advance

Keith Chadwick
Nov 12 '05 #1
2 3333
This KB article states that the use of MSXML within .NET apps is not
supported.
http://support.microsoft.com/default.aspx?kbid=815112

So I would conclude that using System.Xml is the "safer" approach.

-Dino

"Keith Chadwick" <kc*******@leewardsystems.com> wrote in message
news:eL*************@TK2MSFTNGP12.phx.gbl...
I am current in the process of converting an existing ASP application to
ASP.NET. The existing application makes extensive use of server side XML
transformations as in rslt=myxmlobj.tranform(myxsltdoc).

Now I have included the reference to the MSXML 3.0 object into my .NET
application and have it working but I am wondering am I better off using the System.XML object that comes naturally with .NET. Is there a performance
gain? Is it safer for rollout to an ISP? Is it safer to place a
System.xml.xsl.transform object into the application cache versus a
MSXML.DOMDocument30.

Thanks in advance

Keith Chadwick

Nov 12 '05 #2
Thanks, I thought as much. Having used MSXML for a long time I have found
the move to System.xml a little confusing but I appear to be getting over
the hump in just one day, which is not to bad.

Cheers
Keith
"Dino Chiesa [Microsoft]" <di****@online.microsoft.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
This KB article states that the use of MSXML within .NET apps is not
supported.
http://support.microsoft.com/default.aspx?kbid=815112

So I would conclude that using System.Xml is the "safer" approach.

-Dino

"Keith Chadwick" <kc*******@leewardsystems.com> wrote in message
news:eL*************@TK2MSFTNGP12.phx.gbl...
I am current in the process of converting an existing ASP application to
ASP.NET. The existing application makes extensive use of server side XML transformations as in rslt=myxmlobj.tranform(myxsltdoc).

Now I have included the reference to the MSXML 3.0 object into my .NET
application and have it working but I am wondering am I better off using

the
System.XML object that comes naturally with .NET. Is there a performance gain? Is it safer for rollout to an ISP? Is it safer to place a
System.xml.xsl.transform object into the application cache versus a
MSXML.DOMDocument30.

Thanks in advance

Keith Chadwick


Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by Sharon | last post: by
13 posts views Thread by yawnmoth | last post: by
reply views Thread by suresh191 | last post: by
4 posts views Thread by guiromero | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.