Geek Answers Handbook

Running ASP.NET without state view enabled

We are going to start the restoration of one of our ASP.NET projects, and I would like to try to develop it without using viestate (disabled in web.config).

I know about the advantages and disadvantages of viewstate and, generally speaking, that it monitors compared to the control state, however, I would like to know:

  • What are the main differences in the development process? Those. how else do you structure your Page_Load, etc.?

  • Is there any functionality in standard ASP.NET controls that really won’t work without enabling view mode?

Also, are there any detailed articles about workflow differences between working with VS and without VS?

+5
source share
3 answers

Most controls, such as TextBoxes and DropDownLists, will work just fine without a viewstate.

I don’t know about any problems of the development process, except for any controls or properties created or modified using the code, it will not be saved without a viewstate, so you will have to recreate / modify them during the postback.

. , viewstate () . , . 300- - , , 99% viewstate. , , datagrids - , , , , viewstate.

Viewstate:

http://msdn.microsoft.com/en-us/library/ms972976.aspx

+2

viewstate - MVC-? .

+3

I will disable viewstate in my projects. I use scatter / gather methods to populate and retrieve values ​​from aspx pages to / from my data access objects. It is much cleaner and easier than using viewstate.

+2
source

More articles:


All Articles