can i used 1 page's data of viewstate in another page

[vid nandha]

hi all, i have search on net but not satisfied with ans...can anyone tell me that property or data of 1 page's viewstate can be used in another page? Thanx

[r a m e s h]

ViewState cannot be shared between pages. It is specific to a page. Use Session object to share data between pages.

[vid nandha]

thanx but some people telling by server.transfer we can share data....i got that kind of ans from many forums.... some are saying no and some are saying yes..........so i m bit confuse on that..........

[padmanabhan N]

Using Server.Transfer you can not redirect to a different from the server itself. Example if your server is www.yahoo.com you can use server.transfer to move to www.microsoft.com but yes you can move to www.yahoo.com/travels, i.e. within websites. This cross server redirect is possible only using Response.redirect.

Padmanabhan My Articles: Articles[^] My latest Article: Word Automation[^]

[Arindam Sinha]

Have you checked this article[^]? Let me know if this helps you or not. :)

Regards, Arindam Sinha MyBlog - http://arindamsinha.wordpress.com/ Please give your feedback on this answer.

[vid nandha]

i have checked but i cant understand that article.... i m so confused....my que is can we transfer the data from one page to another using view state... that que asked in my interview but i not getting satisfaction yet bcoz some people saying that it can be possible....

[vid nandha]

see this link http://forums.asp.net/t/1137668.aspx[^] by seeing this anyone get confused.........

[padmanabhan N]

What the State Management Types?  Client-side state management stores information on the client’s computer by embedding the information into a web page (Hiddenfields), URL (Query strings) or a cookie. 1. View state. 2. Control state: If you create a custom control that requires view state to work, you should use control state to ensure (يضمن) other developers don’t break your control by disabling view state. 3. Hiddenfields: hidden fields store in HTML form without displaying it in the user’s browser. 4. Cookies: cookies store a value in the user’s browser. 5. Query strings: query string stores values in URL.  Server-side state management stores information on server’s memory. 1. Application state. 2. Session state. 3. Profile Properties. 4. Cache state. What the disadvantages are of ViewState? - Disadvantages of ViewState: 1. The more controls you have on the form the larger the size of ViewState and the larger the size of the HTML you send back and forth to the server. 2. Only works when pages postback to themselves. 3. You can't persist (تحفظ) data to other pages.

Padmanabhan My Articles: Articles[^] My latest Article: Word Automation[^]

[vid nandha]

thanx.........have u seen that link of asp.net forums which i have posted here,in that with examples they have explaine it can be possible so confused n asking....... whats your opinion on that discussion........all that ans were wrong on that?

[padmanabhan N]

actually i am too preparing for interview... in my preparing and experience i have never heard that the viewstate can be transfered from one page to another......

Padmanabhan My Articles: Articles[^] My latest Article: Word Automation[^]

[keyur satyadev]

no. thats specific answer. as per your question specification, answer is no. u can not use viewstate data in other page. so don't go for any forum or other. hope thats fine.

Regards Keyur Satyadev

[Arindam Sinha]

vid nandha wrote:

whats your opinion on that discussion

The opinion is very simple - viewstate is page specific. This should be enough to remove your confusion. Now you mentioned that Server.Transfer with respect to this topic. 1. Server.Trasfer allows you access the instance of the source page. Using that you can access any property defined in that. It's not about accessing the ViewState, it's about accessing the reference of the source page. 2. In practice, a class hides the members which other class can not access. There should be some interfaces (methods) which would allow other classes to interact with the members. Now suppose you have all public properties then what's use of wrapping them. The same thing is applicable here.If you can access the source page's instance in the target page (while Server.Transfer),you can access everything of that page (if you wish) not only the ViewState. As a practice, you can not access ViewState of any page from other page.

Regards, Arindam Sinha MyBlog - http://arindamsinha.wordpress.com/ Please give your feedback on this answer.