Hello there i was using the control state because we have disabled Viewstate
on a particular page. And i noticed that SaveControlState() is called twice.

If you put a trace.warn in SaveControlState you will see it too. It happens
on Visual 2005 and Vs 2008. I tested it on a totally clean page and it
happens there too.

I am wondering is it a bug or is it supposed to be like that? And if it
supposed to work like that, then i would like to know why?

Did you note it by turning trace on? When tracing is enabled it is called
twice to estimate the state size.


--
Teemu Keiski
AspInsider, ASP.NET MVP
http://blogs.aspadvice.com/joteke
http://teemukeiski.net

"MarcusStudentum" <(E-Mail Removed)> wrote in
message news:157238EF-F655-43D9-9970-(E-Mail Removed)...
> Hello there i was using the control state because we have disabled
> Viewstate
> on a particular page. And i noticed that SaveControlState() is called
> twice.
>
> If you put a trace.warn in SaveControlState you will see it too. It
> happens
> on Visual 2005 and Vs 2008. I tested it on a totally clean page and it
> happens there too.
>
> I am wondering is it a bug or is it supposed to be like that? And if it
> supposed to work like that, then i would like to know why?

Cool thanks thats really helpfull. Microsoft should write that bit of
information in
http://msdn2.microsoft.com/en-us/lib...trolstate.aspx

Now i know i should be careful not to change the State in between calls when
Trace is on. I was totally losed because this is a big page with events
firing all over the place.

Cheers
MarcusStudentum

"Teemu Keiski" wrote:

> Did you note it by turning trace on? When tracing is enabled it is called
> twice to estimate the state size.
>
>
> --
> Teemu Keiski
> AspInsider, ASP.NET MVP
> http://blogs.aspadvice.com/joteke
> http://teemukeiski.net
>
> "MarcusStudentum" <(E-Mail Removed)> wrote in
> message news:157238EF-F655-43D9-9970-(E-Mail Removed)...
> > Hello there i was using the control state because we have disabled
> > Viewstate
> > on a particular page. And i noticed that SaveControlState() is called
> > twice.
> >
> > If you put a trace.warn in SaveControlState you will see it too. It
> > happens
> > on Visual 2005 and Vs 2008. I tested it on a totally clean page and it
> > happens there too.
> >
> > I am wondering is it a bug or is it supposed to be like that? And if it
> > supposed to work like that, then i would like to know why?
>
>
>