blocks|key|1118685|text|状态是数据库中的模型。您可以仔细地缓存数据库，以减少页面加载时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1118686|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The state is the model which is in the database. You can carefully cache the database to reduce page load times.

blocks|key|1333813|text|视图状态只是一个又大又难看的隐藏表单域。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1333814|写出您自己的隐藏表单域，并在必要时对它们进行加密。|1333815|幸运的是，不再有任何简单的方法可以将大量数据转储到页面中，因此您必须谨慎选择要保存的内容。|1333816|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

viewstate is just a big, ugly hidden form field. 

Write out your own hidden form fields, and encrypt them if you have to.

Fortunately, there's no longer any simple way to dump lots and lots of data into the page, so you have to be judicious about what you want to save.

blocks|key|1118815|text|MVC中不存在自动生成的视图状态，但您可以简单地使用隐藏字段编写自己的视图状态。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1118816|在MVC中，你不会在页面顶部看到很多你不需要的加密字符。|1118817|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Auto generated view state does not exist in MVC, but you can write your own simply using hidden fields, 

In MVC you will not see a lot of encrypted chars at the top of the page which you don't need most of them.

blocks|key|1333976|text|实际上是这样的。您必须忘记persistance是如何通过viewstate来实现的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1333977|你还必须在你的脑海中将回发转换为“对控制器的调用”。这样以后事情就更容易理解了。不是调用页面，而是调用一个返回视图的控制器。因此，您要么在每次调用时一次又一次地构建整个“页面”，要么决定只处理真正受操作影响的内容。如果按钮更改的是div，为什么要重新加载整个页面。只需调用控制器并在div中返回应该是新数据的内容。|1333978|例如，让我们假设一个主/详细场景：|1333979|<h2>Groups</h2>
++++<div+id="GroupList">
++++</div>
++++<div+id="GroupDetail"+title="Detail+Group">
</div>|code-block|syntax|javascript|1333980|组列表在div中加载一次，并且可以对组列表中的每一项的控制器进行ajax调用：|1333981|<%25=+Ajax.ActionLink("Edit",+"DetailLocalisationGroup",+
+++++++++++++++++++++new+{+id+=+group.Id+},+
+++++++++++++++++++++new+AjaxOptions()+{+
+++++++++++++++++++++++++UpdateTargetId+=+"DetailLocalisationGroup",+
+++++++++++++++++++++++++OnSuccess+=+"InitialisationDetailGroup"+})%25>|1333982|它调用该动作DetailLocalisationGroup，该动作将向div+GroupDetail提供html。|1333983|[AcceptVerbs("POST")]
public+ActionResult+DetailLocalisationGroup(int+id)
{
++++LocalisationGroup+group+=+servicelocalisation.GetLocalisationGroup(id);
++++return+View("DetailGroup",+group);
}|1333984|现在div中有一个表单，当按下该表单的submit按钮时，我们只是将真正需要的信息发送到控制器，然后控制器将数据保存在数据库中。|1333985|在所有这些事件中，GroupList充满了在客户端屏幕上显示的内容，但在那里不需要交互，所以为什么要为这些内容创建视图状态呢……|1333986|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|13|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|14|8|@]|9|@]|A|$]]|$1|Q|3|R|5|H|7|15|8|@]|9|@]|A|$I|J]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|17|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

Actually it does. You have to forget about the way persistance was made up with the viewstate.

You have also to convert in your mind postback onto a page to "call to a controller". This way things will be easier to understand afterwards. Instead of calling a page , you're calling a controller which returns a view. So either your are building your whole "page" again and again on every call, or you decide to deal only with what is really impacted by the action. If the button is changing a div, why reload the entire page. Just make you call to your controller and return what should be the new data in your div.

for example let's imagine a master/detail scenario:

<pre><code>&lt;h2&gt;Groups&lt;/h2&gt;
 &lt;div id="GroupList"&gt;
 &lt;/div&gt;
 &lt;div id="GroupDetail" title="Detail Group"&gt;
&lt;/div&gt;
</code></pre>

The list of group is loaded once in the div and there
is an ajax call possible to a controller for each item of the list of group :

<pre><code>&lt;%= Ajax.ActionLink("Edit", "DetailLocalisationGroup", 
 new { id = group.Id }, 
 new AjaxOptions() { 
 UpdateTargetId = "DetailLocalisationGroup", 
 OnSuccess = "InitialisationDetailGroup" })%&gt;
</code></pre>

which calls this action DetailLocalisationGroup which is to feed the div GroupDetail with html.

<pre><code>[AcceptVerbs("POST")]
public ActionResult DetailLocalisationGroup(int id)
{
 LocalisationGroup group = servicelocalisation.GetLocalisationGroup(id);
 return View("DetailGroup", group);
}
</code></pre>

There is now a form in the div, and when pushing the submit button of this form, we just send the information we really need to a controller which would then save the data in the database.

During all these events, the GroupList was filled with stuff that was displayed on the client screen, but no interaction was needed there and so why bother oneself with a viewstate for these...

blocks|key|1118987|text|所有关于ASP.NET+MVC不使用状态的回答都是正确的。但ASP.NET+MVC实际上确实使用了一些状态，尽管它的工作方式与ViewState完全不同。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1118988|通常，当有人将数据发布到您的应用程序时，您将希望验证数据，并在数据无效时显示错误。但是，如果您只是立即返回包含错误消息的页面，当用户点击F5重新加载页面时，数据将被重新提交。这通常不是你想要的。因此，当您意识到数据POSTed无效时，您希望告诉用户获取页面(或者可能是另一个页面)并显示一条错误消息。您可以通过返回HTTP重定向状态代码来完成此操作。然而，一旦用户的GET请求进入，您如何知道显示什么错误消息呢？您必须以某种方式记住这一点，从您(服务器)处理POST到您处理GET。|1118989|为此，您可以使用一个名为TempData的ASP.NET+MVC特性。这实际上只是一个围绕会话的包装器，它确保您放入TempData字典的任何内容都将保留在那里，直到下一个请求，而不再存在。|1118990|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

All of the answers saying that ASP.NET MVC does not use state are pretty much correct. But ASP.NET MVC does in fact use some state, although it does not work anything like ViewState. 

Usually, when someone POSTs data to your application, you will want to validate the data and display an error if the data are not valid. However, if you just return the page containing the error message immediately, when the user hits F5 to reload the page, the data will be resubmitted. This is usually not what you want. Thus, when you realize that the data POSTed are not valid, you want to tell the users to GET the page (or perhaps another page) and show an error message. You do that by returning an HTTP Redirect status code. However, once the user's GET request comes in, how do you know what error message to display? You will have to somehow remember this from the time you (the server) are handling the POST until you are handling the GET. 

To do this you use an ASP.NET MVC feature called TempData. This is actually just a wrapper around Session which ensures that whatever you shove into the TempData dictionary will stay there until the next request and no longer.

blocks|key|1334099|text|您可以使用MVC3Futures+project模拟视图状态。它将在视图中保存整个模型。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1334100|您所要做的就是序列化模型并在视图中对其进行加密。|1334101|@Html.Serialize("Transfer",+Model,+SerializationMode.EncryptedAndSigned)|code-block|syntax|javascript|1334102|并在控制器中添加反序列化属性。|1334103|public+ActionResult+Transfer(string+id,[Deserialize(SerializationMode.EncryptedAndSigned)]Transfer+transfer)|1334104|entityMap|0|LINK|mutability|MUTABLE|url|http://nuget.org/packages/Mvc3Futures/^0|5|J|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|C|$]]|$1|M|3|N|5|H|7|13|8|@]|9|@]|C|$I|J]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

You can imitate view state with <a href="http://nuget.org/packages/Mvc3Futures/" rel="nofollow">MVC3Futures project</a>. It will save the whole model in view.

All you have to do is to serialize model and encrypt it in view.

<pre><code>@Html.Serialize("Transfer", Model, SerializationMode.EncryptedAndSigned)
</code></pre>

And in controller add deserialized attribute.

<pre><code>public ActionResult Transfer(string id,[Deserialize(SerializationMode.EncryptedAndSigned)]Transfer transfer)
</code></pre>

blocks|key|1119064|text|读完所有这些帖子后，MVC听起来不适合LOB类型的应用程序，在这些应用程序中，您将有许多控件和CRUD操作，并且您希望维护控件的状态。您希望用户停留在同一视图上的原因有很多，即在提交操作完成后保持状态。例如显示错误、服务器端验证消息、成功消息或执行任何其他操作。将用户重定向到其他视图以显示这些消息是不切实际的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1119065|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

After reading all these posts, it sounds like MVC is not good for LOB kind of applications, where you will have lot of controls and, CRUD operations and you want to maintain the state of the controls. There are plenty of reasons where you want the user to stay on the same view &amp; maintain state after submit operations is done. For example to show errors, server side validation messages, success messages, or to perform any other action. redirecting user to some other view to show these messages is not practical.

blocks|key|1119116|text|您可以在会话状态下存储任何对象。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1119117|+HttpContext.Session["userType"]+=+CurrentUser.GetUserType();|code-block|syntax|javascript|1119118|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You can store any object in the session state.

<pre><code> HttpContext.Session["userType"] = CurrentUser.GetUserType();
</code></pre>

I am just looking into converting WebForms to MVC:

In .net MVC, what concepts make ViewState something thats not required?

If a form is posted back on iteself etc (ie a postback)? how does the page/usercontrol maintain its state?

What tricks are people doing to maintain some kind of state and not resort to session state?

Surely, a completely stateless environment cant exist?

asp.net c# MVC: How do I live without ViewState?

数据库

服务器

我只是在研究如何将WebForms转换为MVC：在.net MVC中，哪些概念使得ViewState不是必需的？如果表单被回发到自身等(即回发)？页面/用户控件如何维护其状态？为了保持某种状态而不求助于会话状态，人们在做些什么？当然，一个完全无状态的环境不能存在吗？

问asp.net c# MVC:没有ViewState我该如何生活？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问asp.net c# MVC:没有ViewState我该如何生活？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问asp.net c# MVC:没有ViewState我该如何生活？
EN