prepocessing directives

Results 1 to 3 of 3

Thread: prepocessing directives

  1. #1
    paul foxton Guest

    Default prepocessing directives

    I have a problem being able to include more than one preprocessing directive in my ASP scripts<BR><BR>eg: &#060;%@ LANGUAGE=VBScript %&#062;<BR> &#060;% option explicit %&#062;<BR><BR> &#060;!-- #include virtual = "blah/blah.asp" --&#062;<BR><BR>more than one directive gives me a HTTP 500 internal server error - can anyone help?

  2. #2
    Join Date
    Dec 1969

    Default RE: prepocessing directives

    Not sure about 500 error but you don&#039;t need this:<BR><BR>&#060;%@ LANGUAGE=VBScript %&#062; <BR><BR>as IIS defaults to VBSCRIPT anyway.

  3. #3
    Join Date
    Dec 1969

    Default RE: prepocessing directives

    yeah, I was wondering about that.<BR><BR>Oh well, I&#039;ll just have to drop the &#039;option explicit&#039; directive.<BR>I spose it doesn&#039;t matter so much as long as I build the page with it, will still stop me using undeclared variables and I can take it out when I put in the include.<BR>thanks for the reply Oli

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts