Am I just being thick?

What's wrong with this:

<!--#include file=page8.asp?mrhp -->

I've placed it in an ASP page and run it through both the PWS 4 and IIS 4...

In both cases the server seems to completely ignore the SSI and just leave it on the page like a comment.

While I'm at it...is it ok to pass variables to an included file in an SSI tag (like the "?mrhp" bit above)?

Ok...I figured out what was wrong...the include SSI above statement is placed in the page by an ASP command... so the actual code is like:

<% Response.Write "<!-- #include file=""" & sPage & """ -->"%>

I've realised that the web server does the SSI includes first...then processes ASP script.

Since my SSI is created by the ASP script it isn't there when the server looks for SSIs in the first place.

So...any ideas how I go about including one page in another page dependent on some ASP script?

I.E. How do you get ASP script to write out an SSI?