kay2kay
asked on
report Viewer and Viewstate
I am using the report viewer on my web application. I do not want to turn the viewstate on for the entire application. So the viewstate on the webconfig is turned off
However the viewstate of the page the control is on , the viewstate of the control, the viewstate of the master page have all been turned on.
the control is within a form runat=server
Still, the report viewer errs out with the message asp.net viewstate needs to be enabled.
However the viewstate of the page the control is on , the viewstate of the control, the viewstate of the master page have all been turned on.
the control is within a form runat=server
Still, the report viewer errs out with the message asp.net viewstate needs to be enabled.
...and if you turn on the viewstate on for the entire application, ...does it work...?
ASKER
yes it does.. which we do not want to do.
<which we do not want to do. >
Just curious, ...Why not?
Just curious, ...Why not?
ASKER
We have our own post-back system in place and we don't want to carry the payload of the view state.
OK, then wait for a few other Experts to chime in.
My thought is that perhaps you could turn viewstate on for the entire application, *temporarilly" (Just to get this up and running), until a less burdensome configuration is found.
JeffCoachman
My thought is that perhaps you could turn viewstate on for the entire application, *temporarilly" (Just to get this up and running), until a less burdensome configuration is found.
JeffCoachman
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Understanding the life cycle model and the way master pages are used, helped me fix the issue I had.