RE: [xsl] MSXML question with .NET IDE

Subject: RE: [xsl] MSXML question with .NET IDE
From: "Jon Schwartz \(Volt\)" <a-jonsch@xxxxxxxxxxxxx>
Date: Fri, 16 Apr 2004 14:27:46 -0700
Thinking about your response and David's gave me a bit of a Duh! about
this.  Development based on XSLT is new for me, and Duh!s are not
infrequent yet. :-)

I have two flavors of app I'm working on.  The ASP.NET flavor is doing
transforms on page load on the server side, and is using the proper .NET
framework objects in the proper namespaces.

The other flavor is doing XSLT transforms from client-side script on an
HTML page, using the MSXML 3.0 dll and object model.  For convenience I
am working on that project in the .NET IDE, but there is no project
reference required to MSXML because those objects are used only from
client script, which explicitly creates the ActiveXObjects it needs from
MSXML 3.0.

I think all this means I am not using MSXML from .NET code, and the
initial question was about a reference I do not need.  But your
responses helped me realize that, thanks!  And it's good to know I
officially should NOT use MSXML and .NET together.

Thanks,

Jon

-----Original Message-----
From: Kenny Akridge [mailto:kenny@xxxxxxxxxxxxxxxxx] 
Sent: Friday, April 16, 2004 1:53 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE: [xsl] MSXML question with .NET IDE

If you are using VS 2002 and you did not see this error:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q322174

My guess is that you have something setup incorrectly.

When you added your COM reference, did you use MSXML3.dll?
When you created or objects, for instance DOMDocumentxx, did you use
DOMDocument30?

I have heard of MSXML3 having some major usage problems with .NET




-----Original Message-----
From: Jon Schwartz (Volt) [mailto:a-jonsch@xxxxxxxxxxxxx] 
Sent: Friday, April 16, 2004 1:53 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: [xsl] MSXML question with .NET IDE

Hi all,

I am targeting MSXML 3.0 for my XSLT support, and explicitly selected
that version when I added a reference to my project in VS.NET.  When I
check the properties on the reference, though, they say MSXML 4.0.  Have
any of you seen this and found an explanation of whether we can (or
cannot) trust that the reference is actually to the 3.0 version I
selected?

Thanks in advance,

Jon Schwartz

Current Thread