M
Max Metral
I have a Web.config in my application root dir with the following pages
directive:
<pages buffer="true"
enableViewState="false" enableSessionState="false"
enableViewStateMac="false"/>
And then one in a subdirectory with this one (viewstate enabled):
<pages buffer="true"
enableViewState="true" enableSessionState="false"
enableViewStateMac="true"/>
View state does NOT get enabled in the subdirectory. If I change the pages
directive in the root dir, ViewState goes on. Otherwise, it doesn't. I
can't imagine how this isn't a bug... Any ideas?
As a possible aside, the page in the subdir uses a control, that is also in
the subdir. I put a check in the controls Page_Load of the control to check
ViewState. It thinks it's on.
if (Page.EnableViewState == false || this.EnableViewState == false)
{
Response.Write("Cannot run without view state");
Response.End();
}
Thanks
--max
directive:
<pages buffer="true"
enableViewState="false" enableSessionState="false"
enableViewStateMac="false"/>
And then one in a subdirectory with this one (viewstate enabled):
<pages buffer="true"
enableViewState="true" enableSessionState="false"
enableViewStateMac="true"/>
View state does NOT get enabled in the subdirectory. If I change the pages
directive in the root dir, ViewState goes on. Otherwise, it doesn't. I
can't imagine how this isn't a bug... Any ideas?
As a possible aside, the page in the subdir uses a control, that is also in
the subdir. I put a check in the controls Page_Load of the control to check
ViewState. It thinks it's on.
if (Page.EnableViewState == false || this.EnableViewState == false)
{
Response.Write("Cannot run without view state");
Response.End();
}
Thanks
--max