Some good suggestions going on in this thread; outside of the implementation
details, I'd like to reenforce a few things:
At this time, Microsoft only supports XSLT 1.0 in *all* of its native and
managed XSLT engine implementations . XSLT 2.0 became a recommendation a very
short while ago and we are working towards that end, but the XSLT spec
version is not your issue here.
We have been trying to get the message out: when possible, do not develop
against MSXML 4.0. It's nearing its end of life, which means at some point
in the future it will stop being supported in the browser, and on future
versions of Windows. As others have mentioned, its also an x86-only binary.
When possible use MSXML 6.0. MSXML 6.0 supports ia64 and x64 as well as x86,
and we are working very hard to increase its installed base. If you are
concerned about the currently installed base (re: MSXML 6.0), and are not
redisting MSXML yourself, then develop against MSXML 3.0, which is quite
up-to-date wrt security and reliability and is found on every supported
Windows platform.
IF your issue does in fact turn out to be due to a regression in MSXML 4 on
one sever vs the other, I'd love to know about it. (Pls send a repro my
way.)
"David Wang" <w3*****@gmail. comwrote in message
news:11******** **************@ p10g2000cwp.goo glegroups.com.. .
Do you and your client have the same msxml4.dll binary in %windir%
\System32 ?
msxml4.dll is 32bit-only and does not ship as a part of any version of
Windows, so you both have to install its Redistributable separately...
and the question is whether you are using the same binary version.
I suspect you are not using the same msxml4.dll as your client, and
either you have fix or the customer has a regression in msxml4.dll.
There have been patches of msxml4.dll.
In which case this issue has nothing to do with ASP, IIS6, VC6, nor
ASP.Net, so take back your claims of a nightmare with that
combination! :-)
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
On Feb 15, 10:01 am, "Andrew Wan" <andrew_wan1... @hotmail.comwro te:
Just shooting in the air. Did you specify output type within XSLT file?
For HTML output it should be this:
<xsl:output method="html"/>
Sorry, actually it's outputting html fine. However the logic condition
<xsl:when test="$var = 'here'"></xsl:whenis not working we believe. All
other text variables are assigned correctly using <xsl:variablebu t I
believe the test is failing on our client IIS but works on our IIS.
Is this a possibility?