我可以避免使用杀死viewstate的UpdatePanel吗?-CanIavoidhavinganUpdatePanelthatkillsviewstate?

2  

First I would remove your "filtering" controls from the UpdatePanel. Assuming that the data for these controls are valued on Page_Load, they do not need to be refreshed every time the filter is applied to the GridView. Only the GridView is being refreshed, so it's likely that it is the only control that should be contained in the UpdatePanel.

首先，我将从UpdatePanel删除您的“过滤”控件。假设这些控件的数据值在Page_Load上，它们不需要每次将过滤器应用到GridView时都刷新。只有GridView正在刷新，所以它可能是UpdatePanel中应该包含的惟一控件。

Each of the filtering controls can be added as a trigger for updating the UpdatePanel by declaring them in the section of the UpdatePanel control. Or, if the filtering process is invoked by a "submit" like button, that would be the control to be declared in the section. This should retain the values of the filtering controls in the browser's cache.

通过在UpdatePanel控件的部分中声明更新UpdatePanel，可以添加每个过滤控件作为更新UpdatePanel的触发器。或者，如果筛选过程被“submit”之类的按钮调用，那么这将是要在部分中声明的控件。这将保留浏览器缓存中过滤控件的值。

You can also try Nikhil Kothari's UpdateHistory control (Nikhil has an excellent blog, btw) which will save the contents of the UpdatePanel as history entries in the browser's history list.

您还可以尝试Nikhil Kothari的UpdateHistory控件(Nikhil有一个很棒的博客，顺便说一句)，它将UpdatePanel的内容保存为浏览器历史列表中的历史条目。

EDIT: FYI, UpdatePanel does not "kill" ViewState. The ViewState is transmitted back and forth via the UpdatePanel's update mechanism, often causing performance issues if the ViewState is excessively large. What you're seeing is the browser's history cache not storing the values that have been updated on successive callbacks. The above techniques should help.

编辑:FYI, UpdatePanel不“杀死”ViewState。ViewState通过UpdatePanel的更新机制来回传输，如果ViewState过大，常常会导致性能问题。您看到的是浏览器的历史缓存，没有存储在后续回调中更新的值。上述技术应该会有所帮助。