B
Brad
Hello Everyone,
I was wondering if the following line at the top of my global.asa file is
legal:
<SCRIPT @ENABLESESSIONSTATE = FALSE LANGUAGE = VBSCRIPT RUNAT = SERVER>
It does not produce any errors when I access my site, but since I am mixing
an @ directive with the Language and Runat statements, I just wanted to be
sure. I was also wondering if having the EnableSessionState=False directive
even needs to be included inside the Global.asa file.
At the top of all my .asp files, I have the following:
<%@ENABLESESSIONSTATE = FALSE LANGUAGE = VBSCRIPT%>
<%Option Explicit%>
If I have the EnableSessionState=FALSE in my Global.asa file (and if it's
legal), do I need to have this same statement at the top of all of my .asp
files, or will the setting propagate through the entire application?
Also, I've been wondering why I seem to have to separate the Option Explicit
into other <%%> rather than being able to have all of these statements
within the same <%%> block.
TIA,
~Brad
I was wondering if the following line at the top of my global.asa file is
legal:
<SCRIPT @ENABLESESSIONSTATE = FALSE LANGUAGE = VBSCRIPT RUNAT = SERVER>
It does not produce any errors when I access my site, but since I am mixing
an @ directive with the Language and Runat statements, I just wanted to be
sure. I was also wondering if having the EnableSessionState=False directive
even needs to be included inside the Global.asa file.
At the top of all my .asp files, I have the following:
<%@ENABLESESSIONSTATE = FALSE LANGUAGE = VBSCRIPT%>
<%Option Explicit%>
If I have the EnableSessionState=FALSE in my Global.asa file (and if it's
legal), do I need to have this same statement at the top of all of my .asp
files, or will the setting propagate through the entire application?
Also, I've been wondering why I seem to have to separate the Option Explicit
into other <%%> rather than being able to have all of these statements
within the same <%%> block.
TIA,
~Brad