|
| maybe the XSL file is cached on the client side.
try to purge the cached file in IE
and change the http header options to limit the cache duration in IIS.
"Andrew Wan" <andrew_wan1980@hotmail.com> wrote in message
news:%23ul9%23ggUHHA.4632@TK2MSFTNGP04.phx.gbl...
> 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 Msxml2.DOMDocument.4.0 to transform a
> XML top node via XSL stylesheet outputting to HTML. We have set up the
> website on-site successfully with no problems. However, when we upgraded
> our client some how IIS6 still references a really old XSL file. No matter
> how many times we restart Windows 2003 Server or IIS6, somehow the old XSL
> file is still being used. I then found out about "Lazy Delay Propagation
> for ASP pages". I checked the registry and it's already disabled. I then
> found out about "Uri caching". I disabled that. Still no luck. Why is IIS6
> still referencing the old XSL file?
>
> Even when I remove the "virtual directory" from IIS6, I can't
> modify/rename/delete the actual folder that it was pointing to.
>
> Does anyone know whether there's a conflict issue with IIS6 & MSXML 4.0?
> And no we can't use MSXML 6.0 yet due to our service program using 4.0.
>
|
|