Re: nightmare with ASP, IIS6 & VC6 PSDK

From:

"Alex Blekhman" <xfkt@oohay.moc>

Newsgroups:

microsoft.public.dotnet.framework.aspnet,microsoft.public.inetserver.asp.general,microsoft.public.inetserver.iis,microsoft.public.vc.language,microsoft.public.vc.mfc,microsoft.public.xml,microsoft.public.platformsdk.sdk_install

Date:

Fri, 16 Feb 2007 15:09:34 +0200

Message-ID:

<ONd7zucUHHA.4668@TK2MSFTNGP04.phx.gbl>

"Andrew Wan" wrote:

I am aware there are two XSLT versions (1.0 and 2.0). Also
my conditional logic is like:

<xsl:choose>
<xsl:when test="$var = 'here'"></xsl:when>
<xsl:otherwise>
<xsl:call-template name="Toolbar1"/>
</xsl:otherwise>
</xsl:choose>

When $var does contain 'here', the call-template still
gets executed. So am wondering whether XSLT 2.0 bypasses a
xsl:when clause when it's empty?

First of all, MSXML4 supports XSLT v1.0. Moreover, you must
specify XSLT version with `version' attribute of
`xsl:stylesheet' element:

<xsl:stylesheet
    version="1.0"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
....
</xsl:stylesheet>

Second, you can spare redundant `xsl:otherwise' element if
you use `!=' operator:

<xsl:when test="$var != 'here'">
    ...
</xsl:when>

Actually, in the code you posted, the whole `xsl:choose' can
be replacd with single `xsl:if':

<xsl:if test="$var != 'here'">
    <xsl:call-template name="Toolbar1"/>
</xsl:if>

Also, if you have an access to Visual Studio 2005 or
Altova's XMLSpy, then you will be able to debug XSLT
processing step by step and examine variables during
transformation.

HTH
Alex