blocks|key|1833482|text|始终返回您可以返回的最准确的类型。因此，当操作总是显示视图时，您应该返回一个ViewResult。我只会在某些情况下(无效的提交数据)在ViewResult中返回时才使用ActionResult，或者在其他情况下使用RedirectToRouteResult。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1833483|使用一些高级的操作过滤器/执行场景，你甚至可以返回与ActionResult无关的完全不同的东西。|1833484|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|$]]

Always return the most accurate type you can return. So you should return a ViewResult when the action always shows a view. I would only use ActionResult when you return in ViewResult in some cases (invalid posted data) or a RedirectToRouteResult in other cases. 

With some advanced actionfilter/executing scenario's, you can even return totally different things that have nothing to do with ActionResult.

blocks|key|2047706|text|是的，您可以像这样定义您的操作：public+ViewResult+Index()。但有时您的操作可能会返回不同的结果(不将结果声明为ActionResult基类是不可能的)。例如：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2047707|public+ActionResult+Show()
{
++++...

++++if(Request.IsAjaxRequest())
++++{
++++++++return+PartialView(...);
++++}

++++return+View(...);
}|code-block|syntax|javascript|2047708|或者：|2047709|public+ActionResult+Show()
{
++++...

++++try
++++{
++++++++...
++++}
++++catch(Exception)
++++{
++++++++return+RedirectToAction(...);
++++}

++++return+View(...);
}|2047710|entityMap^0|G|P|1V|C|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|W|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|P|$]]

Yes, you can define your action like: <code>public ViewResult Index()</code>. But sometimes your action can return different results (it is impossible without declaring result as base <code>ActionResult</code> class). For example:

<pre><code>public ActionResult Show()
{
 ...

 if(Request.IsAjaxRequest())
 {
 return PartialView(...);
 }

 return View(...);
}
</code></pre>

or:

<pre><code>public ActionResult Show()
{
 ...

 try
 {
 ...
 }
 catch(Exception)
 {
 return RedirectToAction(...);
 }

 return View(...);
}
</code></pre>

blocks|key|2047777|text|ActionResult是各种返回类型的基类。因此，您的操作必须返回一个ActionResult或从它派生的类才能工作。常见的有ViewResult、JsonResult等。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2047778|entityMap^0|1S|A|23|A|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

ActionResult is the base class for the various return types. So your action must return an ActionResult or a class derived from it in order to work. Common ones are <code>ViewResult</code>, <code>JsonResult</code>, etc.

blocks|key|1833417|text|部分答案:你并不总是返回ActionResult，不。下面是您可以返回的其他一些结果的快速视图：http://msdn.microsoft.com/en-us/library/dd410269%2528v=vs.98%2529.aspx|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1833418|也许这会有一点帮助。祝好运!|1833419|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/dd410269%2528v=vs.98%2529.aspx^0|1C|1U|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

[Partial answer]: You don't always return ActionResult, no. Here's a quick view of some other results you can return: <a href="http://msdn.microsoft.com/en-us/library/dd410269%28v=vs.98%29.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/dd410269%28v=vs.98%29.aspx</a>

Maybe that'll help a little. Good luck!

blocks|key|1833722|text|是的，我有Sanderson的书，我喜欢关于具体的部分，因为当我在看其他控制器动作示例时，这是令我烦恼的事情。我的哲学甚至是b4学习MVC的理念是，由于函数(返回值的方法)应该被视为你在声明一个变量/可以在上下文中替换相同类型的变量/ref，所以对于类型要具体，就像声明一个var一样(可以认为这是为了避免在应用程序中将所有变量定义为类型"Object“--更健壮，但会丢失一些设计时检查和类型安全性)。也便于对正确的返回类型进行控制器单元测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1833723|对于相关的参考，也可以查看Listkov的替换原理(“SOLID”中的"L“)。|1833724|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|$]]

Yep I have Sanderson's book, and I liked that part about being specific, as that was something vexing me when I was looking at other controller action examples. My philosophy even b4 learning MVC was that since functions (methods that return a value) should be treated as if you were declaring a variable/be substitutable in context for a variable/ref of the same type, be specific about the type, as you would if declaring a var (think of it as wanting to avoiding defnining all your variables as type "Object" in an app - more robust, but you lose some design-time checking and type safety). Facilitates a controller unit test for the correct return type as well. 

For related reference, check out Listkov's Substitution Principle (the "L" in "SOLID") also.

Being new to ASP.NET MVC, I've been wondering about the signature of Controller methods. In all the examples I've seen, they always seem to return ActionResult, even if they actually return a ViewResult instance or similar.

Here's a commonly seen example:

<pre><code>public ActionResult Index()
{
 return this.View();
}
</code></pre>

In such a case, wouldn't it make more sense to declare the method as <code>public ViewResult Index()</code>, and get stronger type support?

Experimentation indicates that this works, so it seems possible.

I do realize that there may be situations where the polymorphism is desired (e.g. if you want to redirect only in certain situations, but show a view in other situations), but if the method always returns a view, I'd find a ViewResult more desirable.

In terms of future compatibility, ActionResult obviously provides a more robust signature, but if one controls the entire code base, it's always possible to change a method's signature to a more general return type if that should become necessary in the future.

Are the any other considerations that I'm not aware of, or should I just go ahead and declare my controller methods with specific return types?

Must ASP.NET MVC Controller Methods Return ActionResult?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

作为控制器MVC的新手，我一直想知道ASP.NET方法的签名。在我见过的所有示例中，它们似乎总是返回ActionResult，即使它们实际上返回一个ViewResult实例或类似的实例。下面是一个常见的例子：public ActionResult Index(){    return this.View();}在这种情...

问ASP.NET MVC控制器方法必须返回ActionResult吗？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ASP.NET MVC控制器方法必须返回ActionResult吗？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ASP.NET MVC控制器方法必须返回ActionResult吗？
EN