I'm doing some mods on an ASP Classic site for a client against IIS 5.1 (XP
Pro SP2) running on my laptop or desktop ("localhost"). Everything runs and
looks perfect on these machines. However, when I upload the files to their
web server (IIS 6 on 2003 at a shared hosting company), styles aren't
rendering correctly in the browser. For instance, some colors are wrong, or
some background images don't appear, and some of the ASP script is "breaking"
somehow (things like "end function %>" appear in the rendered HTML).

What's really weird is I can reproduce this behavior on my own 2003/IIS6
server. I copied the files up to it, pointed the browser to it, and bam!
The exact same output as from the web host. Mind you, it's not random
elements failing, but only some, and it's the same ones on both IIS6 boxes.
I have gone through the .CSS file and checked for missing delimiters or
incomplete styles, but there aren't any. Ditto for the .ASP files: nothing
looks "wrong" and I'm not getting any runtime error notifications, either.

What specific things do I need to look for/change in the .CSS or .ASP files
so the site will work correctly on both 5.1 and 6.0? I'm going nucking futs
over this.

Thanks,

IIS is a web server. That means that it only sends back the .css file as-is
to the browser and processes the .asp page on the server to generate HTML
for the client to render (in combination with the .css file that it
downloads). At least, that is what I presume you are doing. If you are doing
some other custom processing, please do explain.

If you see things like "end function %>" from the original ASP script inside
the rendered HTML on the client, it suggests that the ASP page was not
correctly processed on the server-side somehow, and you need to look at how
your ASP page is working. Is it all in one file? Is it including other files
via #include or somehow reading/evaluating script include files? Are you
relying on parent paths or other ASP features whose default values may have
changed on IIS 6?

Because honestly, I cannot think of anything on IIS 5.1 nor IIS 6 default
install that would "change" response data, so we are either looking at bugs
in some custom ISAPI that is installed on your and the web hoster's server
(which would be the responsibility of the provider of the custom ISAPI), or
we are looking at something within ASP (which is what I'm trying to narrow
down).

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
[quoted text, click to view]
I'm doing some mods on an ASP Classic site for a client against IIS 5.1 (XP
Pro SP2) running on my laptop or desktop ("localhost"). Everything runs and
looks perfect on these machines. However, when I upload the files to their
web server (IIS 6 on 2003 at a shared hosting company), styles aren't
rendering correctly in the browser. For instance, some colors are wrong, or
some background images don't appear, and some of the ASP script is
"breaking"
somehow (things like "end function %>" appear in the rendered HTML).

What's really weird is I can reproduce this behavior on my own 2003/IIS6
server. I copied the files up to it, pointed the browser to it, and bam!
The exact same output as from the web host. Mind you, it's not random
elements failing, but only some, and it's the same ones on both IIS6 boxes.
I have gone through the .CSS file and checked for missing delimiters or
incomplete styles, but there aren't any. Ditto for the .ASP files: nothing
looks "wrong" and I'm not getting any runtime error notifications, either.

What specific things do I need to look for/change in the .CSS or .ASP files
so the site will work correctly on both 5.1 and 6.0? I'm going nucking futs
over this.

Thanks,
Alan