473,237 Members | 1,266 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,237 software developers and data experts.

nightmare with ASP, IIS6 & VC6 PSDK

I have been having a nightmare with ASP/ASP.NET & IIS6.

We use Msxml2.DOMDocument.4.0 object to create a XML object in ASP. The
Msxml2.DOMDocument.4.0 is from the Windows Platform SDK Feb 2003 (the last
version compatible with VC6). Then we use
TranslateXSLT(XMLDocument.transformNode) passing in a xsl file path. Our
pages work perfectly fine under IIS5 & IIS6 onsite. However strange things
happening at our clients IIS6:

- transformation just displays the xml nodes instead of the html code.

Probably it's nothing to do with IIS6. Maybe it's Msxml2.DOMDocument.4.0
from Platform SDK Feb 2003?

Anyone has any ideas?


Feb 15 '07 #1
10 2085
"Andrew Wan" wrote:
I have been having a nightmare with ASP/ASP.NET & IIS6.

We use Msxml2.DOMDocument.4.0 object to create a XML
object in ASP. The
Msxml2.DOMDocument.4.0 is from the Windows Platform SDK
Feb 2003 (the last
version compatible with VC6). Then we use
TranslateXSLT(XMLDocument.transformNode) passing in a xsl
file path. Our
pages work perfectly fine under IIS5 & IIS6 onsite.
However strange things
happening at our clients IIS6:

- transformation just displays the xml nodes instead of
the html code.

Probably it's nothing to do with IIS6. Maybe it's
Msxml2.DOMDocument.4.0
from Platform SDK Feb 2003?

Just shooting in the air. Did you specify output type within
XSLT file? For HTML output it should be this:

<xsl:output method="html"/>
Alex
Feb 15 '07 #2
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:variablebut I
believe the test is failing on our client IIS but works on our IIS.

Is this a possibility?
Feb 15 '07 #3
"Andrew Wan" wrote:
>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:when>
is not working we believe. All other text variables are
assigned correctly using <xsl:variablebut I believe the
test is failing on our client IIS but works on our IIS.

Is this a possibility?

I have hard time believeing that the same version of XSLT
processor behaves differently on other machine. Probably
`$var' contains something different than "here". You can try
`ms:string-compare' function if you need case insensitive or
language dependant comparison.

Alex

Feb 15 '07 #4
Andrew,
Is this classic ASP? If so, you're posting to the ASP.NET Group. Try the asp
group.
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"Andrew Wan" wrote:
I have been having a nightmare with ASP/ASP.NET & IIS6.

We use Msxml2.DOMDocument.4.0 object to create a XML object in ASP. The
Msxml2.DOMDocument.4.0 is from the Windows Platform SDK Feb 2003 (the last
version compatible with VC6). Then we use
TranslateXSLT(XMLDocument.transformNode) passing in a xsl file path. Our
pages work perfectly fine under IIS5 & IIS6 onsite. However strange things
happening at our clients IIS6:

- transformation just displays the xml nodes instead of the html code.

Probably it's nothing to do with IIS6. Maybe it's Msxml2.DOMDocument.4.0
from Platform SDK Feb 2003?

Anyone has any ideas?


Feb 16 '07 #5
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.comwrote:
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:variablebut I
believe the test is failing on our client IIS but works on our IIS.

Is this a possibility?
Feb 16 '07 #6
try here:

microsoft.public.xsl

"Peter Bromberg [C# MVP]" <pb*******@yahoo.yabbadabbadoo.comwrote in message
news:A4**********************************@microsof t.com...
Andrew,
Is this classic ASP? If so, you're posting to the ASP.NET Group. Try the asp
group.
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"Andrew Wan" wrote:
>I have been having a nightmare with ASP/ASP.NET & IIS6.

We use Msxml2.DOMDocument.4.0 object to create a XML object in ASP. The
Msxml2.DOMDocument.4.0 is from the Windows Platform SDK Feb 2003 (the last
version compatible with VC6). Then we use
TranslateXSLT(XMLDocument.transformNode) passing in a xsl file path. Our
pages work perfectly fine under IIS5 & IIS6 onsite. However strange things
happening at our clients IIS6:

- transformation just displays the xml nodes instead of the html code.

Probably it's nothing to do with IIS6. Maybe it's Msxml2.DOMDocument.4.0
from Platform SDK Feb 2003?

Anyone has any ideas?



Feb 16 '07 #7
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?

"Alex Blekhman" <xf**@oohay.mocwrote in message
news:ed**************@TK2MSFTNGP04.phx.gbl...
"Andrew Wan" wrote:
>>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:variablebut I
believe the test is failing on our client IIS but works on our IIS.

Is this a possibility?


I have hard time believeing that the same version of XSLT processor
behaves differently on other machine. Probably `$var' contains something
different than "here". You can try `ms:string-compare' function if you
need case insensitive or language dependant comparison.

Alex

Feb 16 '07 #8

"Andrew Wan" <an************@hotmail.comwrote in message
news:e9**************@TK2MSFTNGP02.phx.gbl...
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?

I note this Q has not yet appeared in microsoft.public.xsl. You really
should post it there you will get more focused support there than here.
Feb 16 '07 #9
"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

Feb 16 '07 #10
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.googlegr oups.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.comwrote:
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:variablebut I
believe the test is failing on our client IIS but works on our IIS.

Is this a possibility?

Feb 16 '07 #11

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

36
by: Thomas | last post by:
after spending countless hours trying, i give up and hope to get some help in here. on server1 i got the web myweb.com with my test.asp. in the test.asp, i'm trying to read a file from an UNC...
1
by: Mark Fancy | last post by:
I have a project that I'm trying to get to compile. I need to have the /Tc:wchar_t compile switch in order to use some libraries. I have included the following header files: #include <mapix.h>...
2
by: Eric Sanders | last post by:
Where can I find these two files: ntrtl.h & nturtl.h? I evidently need them included in my project, but I keep getting "No such file or directory" when including them. I have downloaded the...
5
by: Terry Strachan | last post by:
Hi, I have an asp.net webapp that works fine on my development machine, win2k/iis5 however, when I move the site across to win2k3 / iis6 i get the following error on postback of any page; ...
1
by: Luwk | last post by:
I have an application that communicates with the Company's Active Directory to get the OU of the users. This said application is an ASP.Net web site and has the Windows Authentication enabled. ....
10
by: Andrew Wan | last post by:
I have been having a nightmare with ASP/ASP.NET & IIS6. We use Msxml2.DOMDocument.4.0 object to create a XML object in ASP. The Msxml2.DOMDocument.4.0 is from the Windows Platform SDK Feb 2003...
2
by: Andrew Wan | last post by:
Okay, this is really weird. We have two Windows 2003 Server SP1 PCs. One hosts IIS6 website, and the other hosts our DCOM service program. Our website is ASP/XSL. An ASP page uses...
1
by: lilOlMe | last post by:
Can you install IIS6 on a system other than Windows Server 2003? I'd like to install IIS6 on Windows XP. I've been trying to find out the system requirements for IIS6 but I haven't found a clear...
11
by: Charles E Hardwidge | last post by:
I feel a bit dumb for asking this but I lost my documentation in an accident. Could someone confirm the last supported PSDK for VC2003 and 95/98/ME & NT4? -- Charles E Hardwidge
0
by: abbasky | last post by:
### Vandf component communication method one: data sharing ​ Vandf components can achieve data exchange through data sharing, state sharing, events, and other methods. Vandf's data exchange method...
0
by: fareedcanada | last post by:
Hello I am trying to split number on their count. suppose i have 121314151617 (12cnt) then number should be split like 12,13,14,15,16,17 and if 11314151617 (11cnt) then should be split like...
0
Git
by: egorbl4 | last post by:
Скачал я git, хотел начать настройку, а там вылезло вот это Что это? Что мне с этим делать? ...
1
by: davi5007 | last post by:
Hi, Basically, I am trying to automate a field named TraceabilityNo into a web page from an access form. I've got the serial held in the variable strSearchString. How can I get this into the...
0
by: MeoLessi9 | last post by:
I have VirtualBox installed on Windows 11 and now I would like to install Kali on a virtual machine. However, on the official website, I see two options: "Installer images" and "Virtual machines"....
0
by: DolphinDB | last post by:
The formulas of 101 quantitative trading alphas used by WorldQuant were presented in the paper 101 Formulaic Alphas. However, some formulas are complex, leading to challenges in calculation. Take...
0
by: DolphinDB | last post by:
Tired of spending countless mintues downsampling your data? Look no further! In this article, you’ll learn how to efficiently downsample 6.48 billion high-frequency records to 61 million...
0
by: Aftab Ahmad | last post by:
So, I have written a code for a cmd called "Send WhatsApp Message" to open and send WhatsApp messaage. The code is given below. Dim IE As Object Set IE =...
0
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.