re:
!To be clear by viewstate I am referring to hidden form fields
You mean that viewstate uses *one* hidden field ( singular ).
Other hidden fields don't hold StateBag information.
re:
!ControlState:
!
http://msdn2.microsoft.com/en-us/library/ms178577.aspx
!Isn't the bulk of control state still persisted in the hidden _viewstate field ?
No. You don't have to have Viewstate enabled in order to be able to use ControlState.
Review the link provided above...
re:
!Assuming we are extending a web control and say we created a new property as part
!of this control. The user of this control sets the initial value of the property declaratively
!through the property window or as part of the html markup.
!Now one of the server side event changes the value of this property, where is the
!new value stored, how will the framework track the changes to the property,
!what are the placeholders for the framework to determine if the value is dirty.
While that sounds like an interesting theoretical proposition,
I haven't found the need to do that in any application I've developed.
re:
!I presume everything does eventually end up in hidden fields, don't they?
You may be presuming a bit too much.
;-)
Juan T. Llibre, asp.net MVP
asp.net faq :
http://asp.net.do/faq/
foros de asp.net, en español :
http://asp.net.do/foros/
=============== =============== ========
"Raaj" <ra***********@ yahoo.comwrote in message
news:11******** *************@x 35g2000prf.goog legroups.com...
To be clear by viewstate I am referring to hidden form fields
(explanation below)
>re:
!What are such alternate methods?
ControlState:
http://msdn2.microsoft.com/en-us/library/ms178577.aspx
I still wonder if this makes a difference. Isn't the bulk of control
state still persisted in the hidden _viewstate field, eventually the
state of the controls go through the round trip
So if the original post was restated as "How can I reduce the hidden
fields for my asp.net application? It is getting very large now. What
is a good solution? "What would be the probable answer?
re:
!So, How do you manage (without viewstate) to track declarative and
!dynamic changes to the properties of server controls?
>Can you describe a real-life example of needing to do that with viewstate ?
Assuming we are extending a web control and say we created a new property as part
of this control. The user of this control sets the initial value of the property declaratively
through the property window or as part of the html markup.
Now one of the server side event changes the value of this property, where is the
new value stored, how will the framework track the changes to the property,
what are the placeholders for the framework to determine if the value is dirty.
I presume everything does eventually end up in hidden fields, don't they?
>I prefer alternate methods of persisting the page/control info viewstate persists
It appears you are persisting the state of the controls through the
hidden fields
On Jun 11, 4:00 pm, "Juan T. Llibre" <nomailrepl...@ nowhere.com>
wrote:
re:
!So, How do you manage (without viewstate) to track declarative and
!dynamic changes to the properties of server controls?
Can you describe a real-life example of needing to do that with viewstate ?
re:
!What are such alternate methods?
ControlState:
http://msdn2.microsoft.com/en-us/library/ms178577.aspx
re:
!somehow I'am not quite sure where do you persist the
!controls properties state without viewstate
Read up on ControlState.
To read Microsoft's recommendations for maintaining state across a wide range of properties, see :
http://msdn2.microsoft.com/en-us/library/z1hkazw7.aspx
Juan T. Llibre, asp.net MVP
asp.net faq :http://asp.net.do/faq/
foros de asp.net, en español :http://asp.net.do/foros/
=============== =============== ========"Raaj" <raaj.umapa...@ yahoo.comwrote in message
news:11******** **************@ q69g2000hsb.goo glegroups.com.. .
Juan,
I've never missed viewstate because I never program against the viewstate.
So, How do you manage (without viewstate) to track declarative and
dynamic changes to the properties of server controls?
I prefer alternate methods of persisting the page/control info viewstate persists.
Viewstate is only one of several ways to persist page/control info you're interested in.
What are such alternate methods?
ASP.NET automatically populates control values with the data from Request.Form,
however, and I prefer using Session values to persist other types of data.
True, as long as the controls implement IPostBackDataHa ndler
interface. But somehow I'am not quite sure where do you persist the
controls properties state without viewstate
I am not trying to be nit picky, curious to know how you are managing
things differently.
Raaj
On Jun 11, 8:43 am, "Juan T. Llibre" <nomailrepl...@ nowhere.com>
wrote:
re:
!Be careful, in many cases viewstate needs to be enabled.
Which cases *need* viewstate ?
I've never missed viewstate because I never program against the viewstate.
I prefer alternate methods of persisting the page/control info viewstate persists.
Viewstate is only one of several ways to persist page/control info you're interested in.
Viewstate contains all of a page's information *except* the data
which is available in the Request.Form collection, (PostData).
ASP.NET automatically populates control values with the data from Request.Form,
however, and I prefer using Session values to persist other types of data.
Juan T. Llibre, asp.net MVP
asp.net faq :http://asp.net.do/faq/
foros de asp.net, en español :http://asp.net.do/foros/
=============== =============== ========"Eliyah u Goldin"
<REMOVEALLCAPIT ALSeEgGoldD...@ mMvVpPsS.org>
wrote in message
news:uQ******** ******@TK2MSFTN GP04.phx.gbl...
Be careful, in many cases viewstate needs to be enabled. You can set EnableViewState ="false"
on
the page level and EnableViewState ="true" for individual controls that need it.
--
Eliyahu Goldin,
Software Developer & Consultant
Microsoft MVP [ASP.NET]
>http://msmvps.com/blogs/egoldin
>http://usableasp.net
"Juan T. Llibre" <nomailrepl...@ nowhere.comwrot e in message
>news:%2******* *********@TK2MS FTNGP02.phx.gbl ...
>re:
>!How can i reduce the viewstate for my asp.net application.
><%@ Page Language="C#" EnableViewState ="false" %>
>or
><%@ Page Language="VB" EnableViewState ="false" %>
>Juan T. Llibre, asp.net MVP
>asp.net faq :http://asp.net.do/faq/
>foros de asp.net, en español :http://asp.net.do/foros/
>============== =============== =========
>"Nick C" <bef...@gmail.c omwrote in messagenews:eX* *************@T K2MSFTNGP02.phx .gbl...
>>Hi
>>How can i reduce the viewstate for my asp.net application. It is getting very large now.
>>What
>>is
>>a good solution?
>>thanks
>>N- Hide quoted text -
- Show quoted text -- Hide quoted text -
- Show quoted text -
