blocks|key|222358|text|WebAPI去掉了OData，因此您可以获得使用OData的所有优点。例如，使用WebAPI时，您将获得：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|222359|222360|查询选项，如$filter、$top、$orderby等。|unordered-list-item|222361|使用传统的MVC控制器，您需要实施这些yourself.|222362|222363|222364|​|222365|222366|Standardization+of+the+format++API.|222367|有一些可理解RESTful+|222368|的底层格式的OData客户端|222369|222370|222371|entityMap^0|0|0|1|1|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Y|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|Z|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|M|3|N|5|E|7|14|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|15|8|@]|9|@]|A|$]]|$1|Q|3|R|5|E|7|16|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|T|3|K|5|6|7|18|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|V|$]]

WebAPI spits out OData, so you get all of the advantages of using OData. For example, with WebAPI you get:

<ul>
<li>Query options such as $filter, $top, $orderby, etc.
<ul>
<li>With traditional MVC controllers you need to implement these yourself.</li>
</ul></li>
<li>Standardization of the format 
<ul>
<li>There are OData clients that will understand the underlying format of your RESTful API.</li>
</ul></li>
</ul>

blocks|key|2872987|text|WebApi允许创建可以通过超文本传输协议公开的服务，而不是通过正式的服务。另一个不同之处在于WebApi如何使用Http协议并使其成为真正的Http一等公民。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2872988|更新：的核心，Web已经集成到ASP.NET项目类型中。ApiController类被合并到Controller类中。更多信息请访问：https://wildermuth.com/2016/05/10/Writing-API-Controllers-in-ASP-NET-MVC-6|offset|length|style|BOLD|CODE|2872989|相关的比较、讨论和教程链接：|2872990|2872991|MVC5+vs+WebApi+Project+|unordered-list-item|2872992|Difference+between+ASP.NET+MVC+and+ASP.NET+Web+API|2872993|Introduction+to+ASP.NET+Core包括MVC、Web+demos|2872994|Getting+Started+with+ASP.NET+Web+API+tutorials|2872995|2872996|​|2872997|📷|atomic|2872998|2872999|entityMap|0|LINK|mutability|MUTABLE|url|https://wildermuth.com/2016/05/10/Writing-API-Controllers-in-ASP-NET-MVC-6|1|https://stackoverflow.com/questions/22589245/difference-between-mvc-5-project-and-web-api-project|2|http://www.dotnettricks.com/learn/webapi/difference-between-aspnet-mvc-and-aspnet-web-api|3|https://mva.microsoft.com/en-US/training-courses/introduction-to-aspnet-core-with-visual-studio-2017-16841?l=Mn1Ba0CgD_3201937555|4|https://docs.microsoft.com/en-us/aspnet/web-api/overview/getting-started-with-aspnet-web-api/|5|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/07a6f4364fd83bfe6b3d7f8a26e855b2.jpeg|imageAlt^0|0|0|3|S|D|1A|A|1V|22|0|0|0|0|0|M|1|0|0|1E|2|0|0|S|3|0|0|10|4|0|0|0|0|1|5|0|0^^$0|@$1|2|3|4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1O|8|@$D|1P|E|1Q|F|G]|$D|1R|E|1S|F|H]|$D|1T|E|1U|F|H]]|9|@$D|1V|E|1W|1|1X]]|A|$]]|$1|I|3|J|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|20|8|@]|9|@$D|21|E|22|1|23]]|A|$]]|$1|O|3|P|5|N|7|24|8|@]|9|@$D|25|E|26|1|27]]|A|$]]|$1|Q|3|R|5|N|7|28|8|@]|9|@$D|29|E|2A|1|2B]]|A|$]]|$1|S|3|T|5|N|7|2C|8|@]|9|@$D|2D|E|2E|1|2F]]|A|$]]|$1|U|3|-4|5|6|7|2G|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|2H|8|@]|9|@]|A|$]]|$1|X|3|Y|5|Z|7|2I|8|@]|9|@$D|2J|E|2K|1|2L]]|A|$]]|$1|10|3|W|5|6|7|2M|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|2N|8|@]|9|@]|A|$]]]|12|$13|$5|14|15|16|A|$17|18]]|19|$5|14|15|16|A|$17|1A]]|1B|$5|14|15|16|A|$17|1C]]|1D|$5|14|15|16|A|$17|1E]]|1F|$5|14|15|16|A|$17|1G]]|1H|$5|1I|15|1J|A|$1K|1L|1M|-4]]]]

WebApi allows to create services that can be exposed over HTTP rather than through a formal service such as WCF or SOAP. 
Another difference is in the way how WebApi uses Http protocol and makes it truly First class Http citizen.

UPDATE: The ASP.NET Core, Web API has been integrated into MVC project type. The <code>ApiController</code> class is consolidated into the <code>Controller</code> class. More at: <a href="https://wildermuth.com/2016/05/10/Writing-API-Controllers-in-ASP-NET-MVC-6" rel="noreferrer">https://wildermuth.com/2016/05/10/Writing-API-Controllers-in-ASP-NET-MVC-6</a>

A relevant link of comparison, discussions &amp; tutorials: 

<ul>
<li><a href="https://stackoverflow.com/questions/22589245/difference-between-mvc-5-project-and-web-api-project">MVC5 vs WebApi Project</a> </li>
<li><a href="http://www.dotnettricks.com/learn/webapi/difference-between-aspnet-mvc-and-aspnet-web-api" rel="noreferrer">Difference between ASP.NET MVC and
ASP.NET Web API</a></li>
<li><a href="https://mva.microsoft.com/en-US/training-courses/introduction-to-aspnet-core-with-visual-studio-2017-16841?l=Mn1Ba0CgD_3201937555" rel="noreferrer">Introduction to ASP.NET Core</a> includes MVC, Web API demos</li>
<li><a href="https://docs.microsoft.com/en-us/aspnet/web-api/overview/getting-started-with-aspnet-web-api/" rel="noreferrer">Getting Started with ASP.NET Web API</a> tutorials</li>
</ul>

<a href="https://i.stack.imgur.com/Af5xg.jpg" rel="noreferrer"><img src="https://i.stack.imgur.com/Af5xg.jpg" alt="enter image description here"></a>

blocks|key|222274|text|在某种程度上，你可能想一起忘记ASP.NET+MVC。如果您是一名.NET开发人员，但是想要构建一个单页面应用程序(例如，使用Angular+)，那么您将希望获得RESTful服务(WebAPI)的好处，同时又不想要ASP.NET+MVC带来的所有不必要的臃肿。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|222275|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|$]]

At some point you might want to forget ASP.NET MVC all together. If you are a .NET developer but you want to build a Single-Page application (using Angular for instance) you'll want the benefits of a RESTful service (WebAPI) without all of the unnecessary bloat that comes with ASP.NET MVC.

blocks|key|222427|text|相似性|type|unstyled|depth|inlineStyleRanges|entityRanges|data|222428|222429|和ihttphandler都继承了异步创建的功能，所以基本上都是web.http|ordered-list-item|offset|length|style|CODE|222430|的包装器|222431|差异：|222432|222433|MVC控制器非常繁重，如果您可以查看它的定义，您可以看到它使用了多少接口和基本代码，web+API是较轻的控制器，并通过其传递的参数来区分请求(是的，我们也可以更改它！)|222434|222435|222436|MVC控制器有太多的功能，如返回视图、动作结果、javascript结果等，但在web+API中只有JSON或XML。|222437|222438|+MVC用于实现Restful(GET，POST，PUT，DELETE，OPTIONS)服务，这些服务可以独立地托管在任何地方，而不依赖于视图，|222439|控制器无法支持这一点，因为它与视图紧密集成。|222440|222441|entityMap^0|0|0|1|C|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|14|8|@$F|15|G|16|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|18|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|O|3|P|5|E|7|1A|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|S|3|T|5|E|7|1D|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1F|8|@]|9|@]|A|$]]|$1|X|3|Y|5|E|7|1G|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|11|$]]

Similarities
<ol>
<li>both inherits from <code>ihttphandler</code> for the asyncrequest so basically apicontroller or mvc controller both are the wrapper around the web.http</li>
</ol>
Differences:
<ol>
<li>MVC controller is very heavy if you could go through its definition you can see how many interfaces and the base code it has used, web API is lighter controller and distinguish request by its passed parameters ( yes we can change it too!)
</li>
<li>MVC controller has too many features like it return views, action result, javascript result, etc but in web API has either JSON or XML.
</li>
<li>API is for implementing Restful(GET, POST, PUT, DELETE, OPTIONS) services which can be independently hosted anywhere without the depending upon views, MVC controller cant support that as it tightly integrated with the views.
</li>
</ol>

blocks|key|219257|text|通常，WebAPI用于数据服务，其中MVC可以生成更多类型的输出。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|219258|WebAPI无疑简化了我们创建数据服务的方式。对于这个目的来说，它是干净和简单的。MVC提供了更多的工具。|219259|MVC可以生成WebAPI可以输出的任何输出。从模板生成输出可以在MVC中轻松实现。我在WebAPI中找不到这样做的理由。PHP开发人员和老的ASP程序员可能从过去知道这种态度，在那里你可以在里面构建与C#代码相关的HTML文件。|219260|WebAPI-+DATA+MVC+-+DATA、UI/HTML、XHTML、Files、Templates等。|219261|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Usually,
WebAPI used for data services where MVC can generate more types of outputs.

WebAPI for sure simplifies the way we can create data services.
It's clean and easy for this purpose.
MVC come with some more tools around.

MVC can generate any output WebAPI can output.
Generating outputs from templates can be easily achieved in MVC. I can't find a reason to do so in WebAPI. PHP developers and old ASP programmer might know this attitude from the past, where you can build HTML files involved with C# code inside.

WebAPI- DATA
MVC - DATA, UI/HTML, XHTML, Files, Templates etc..

blocks|key|3086939|text|ASP.NET+MVC和ASP.NET+Web+api的用途各不相同|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3086940|ASP.NET|offset|length|style|BOLD|3086941|ASP.NET提供了三个用于创建web应用程序的框架:+Web窗体、Web和ASP.NET网页。这三个框架都是稳定和成熟的，你可以使用它们中的任何一个来创建伟大的web应用程序。无论您选择哪种框架，您都可以随时随地获得ASP.NET的所有好处和特性。|3086942|每个框架都针对不同的开发风格。您选择哪一个取决于您的编程资产(知识、技能和开发经验)、您正在创建的应用程序的类型以及您熟悉的开发方法的组合。所有这三个框架都将在ASP.NET的未来版本中得到支持、更新和改进。|3086943|MVC|3086944|ASP.NET+MVC为您提供了一种强大的、基于模式的方式来构建动态网站，这种方式可以实现清晰的关注点分离，并使您能够完全控制标记，从而实现愉快、敏捷的开发。TDD包括许多特性，这些特性支持快速、ASP.NET友好的开发，以创建使用最新web标准的复杂应用程序。|3086945|网络应用编程接口|3086946|HTTP是一个框架，它使构建ASP.NET服务变得很容易，这些服务可以到达广泛的客户端，包括浏览器和移动设备。ASP.NET+Web+API是在.NET框架上构建RESTful应用程序的理想平台。|3086947|你可以在这里阅读更多表格http://www.dotnet-tricks.com/Tutorial/webapi/Y95G050413-Difference-between-ASP.NET-MVC-and-ASP.NET-Web-API.html|3086948|entityMap|0|LINK|mutability|MUTABLE|url|http://www.dotnet-tricks.com/Tutorial/webapi/Y95G050413-Difference-between-ASP.NET-MVC-and-ASP.NET-Web-API.html^0|0|0|7|0|0|0|0|3|0|0|0|8|0|0|C|33|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@$D|15|E|16|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|17|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|18|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|19|8|@$D|1A|E|1B|F|G]]|9|@]|A|$]]|$1|N|3|O|5|6|7|1C|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1D|8|@$D|1E|E|1F|F|G]]|9|@]|A|$]]|$1|R|3|S|5|6|7|1G|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1H|8|@]|9|@$D|1I|E|1J|1|1K]]|A|$]]|$1|V|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]]|W|$X|$5|Y|Z|10|A|$11|12]]]]

ASP.NET MVC And ASP.NET Web api both of them are using for different purpose

ASP.NET

ASP.NET offers three frameworks for creating web applications: Web Forms, ASP.NET MVC, and ASP.NET Web Pages. All three frameworks are stable and mature, and you can create great web applications with any of them. No matter what framework you choose, you will get all the benefits and features of ASP.NET everywhere.

Each framework targets a different development style. The one you choose depends on a combination of your programming assets (knowledge, skills, and development experience), the type of application you’re creating, and the development approach you’re comfortable with. All three frameworks will be supported, updated, and improved in future releases of ASP.NET.

MVC

ASP.NET MVC gives you a powerful, patterns-based way to build dynamic websites that enables a clean separation of concerns and that gives you full control over markup for enjoyable, agile development. ASP.NET MVC includes many features that enable fast, TDD-friendly development for creating sophisticated applications that use the latest web standards.

Web API

ASP.NET Web API is a framework that makes it easy to build HTTP services that reach a broad range of clients, including browsers and mobile devices. ASP.NET Web API is an ideal platform for building RESTful applications on the .NET Framework.

you can read more form here
<a href="http://www.dotnet-tricks.com/Tutorial/webapi/Y95G050413-Difference-between-ASP.NET-MVC-and-ASP.NET-Web-API.html" rel="noreferrer">http://www.dotnet-tricks.com/Tutorial/webapi/Y95G050413-Difference-between-ASP.NET-MVC-and-ASP.NET-Web-API.html</a>

blocks|key|219272|text|这张图片似乎显示了问题的不同和相似之处。我希望这对我很有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|219273|​|219274|📷|atomic|offset|length|219275|219276|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/1d56156b6265c4de4c0ca0d5177b1940.jpeg|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

This image seems to show the differences and similarities in the way the matter. I hope that helps is interesting for me.

<a href="https://i.stack.imgur.com/95usu.jpg" rel="noreferrer"><img src="https://i.stack.imgur.com/95usu.jpg" alt="enter image description here"></a>

blocks|key|2873165|text|Asp.Net网络应用编程接口与Asp.Net+MVC|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2873166|📷|atomic|2873167|1。HTTP用于创建同时返回视图和数据的web应用程序，而Asp.Net+Web+API用于创建完全成熟的Asp.Net服务，其方法简单，只返回数据而不返回视图。|2873168|2。Web有助于在.NET框架上构建REST-ful服务，它还支持内容协商(它是关于决定客户端可以接受的最佳响应格式数据。它可以是JSON、XML、ATOM或其他格式化数据)，不在MVC中的自托管。|2873169|3。Web+API还负责根据请求中的Accept头返回特定格式的数据，如JSON、XML或任何其他格式，您不必担心这一点。MVC使用JsonResult只返回JSON格式的数据。|2873170|4。在Web+API中，请求被映射到基于HTTP谓词的操作，而在MVC中，请求被映射到操作名称。|2873171|5。Asp.Net+Web+API是一个新的框架，是核心ASP.NET框架的一部分。Web中存在的模型绑定、过滤器、路由和其他MVC特性不同于MVC，并且存在于新的System.Web.Http程序集中。在MVC中，这些特性存在于System.Web.Mvc中。因此，Web+API还可以与Asp.Net一起使用，并作为独立的服务层使用。|2873172|6。您可以在单个项目中混合使用Web+API和MVC控制器，以处理可能以JSON、XML或任何其他格式返回数据的高级AJAX请求，并构建一个成熟的HTTP服务。通常，这将称为Web+API自托管。|2873173|7。当您拥有混合的MVC和Web+API控制器并希望实现授权时，您必须创建两个过滤器，一个用于MVC，另一个用于Web+API，因为这两个过滤器是不同的。|2873174|8。此外，Web+API是轻量级架构，除了web应用程序外，它还可以与智能手机应用程序一起使用。|2873175|原始源为here|2873176|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/c0dde051256e09bc5660771e1635b6d4.png|imageAlt|1|LINK|MUTABLE|url|http://www.dotnettricks.com/learn/webapi/difference-between-aspnet-mvc-and-aspnet-web-api^0|0|R|0|0|1|0|0|0|1|0|0|1|0|0|1|0|0|1|0|0|1|0|0|1|0|0|1|0|0|1|0|4|4|1|0^^$0|@$1|2|3|4|5|6|7|1E|8|@$9|1F|A|1G|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1H|8|@]|D|@$9|1I|A|1J|1|1K]]|E|$]]|$1|I|3|J|5|6|7|1L|8|@$9|1M|A|1N|B|C]]|D|@]|E|$]]|$1|K|3|L|5|6|7|1O|8|@$9|1P|A|1Q|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|1R|8|@$9|1S|A|1T|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|1U|8|@$9|1V|A|1W|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1X|8|@$9|1Y|A|1Z|B|C]]|D|@]|E|$]]|$1|S|3|T|5|6|7|20|8|@$9|21|A|22|B|C]]|D|@]|E|$]]|$1|U|3|V|5|6|7|23|8|@$9|24|A|25|B|C]]|D|@]|E|$]]|$1|W|3|X|5|6|7|26|8|@$9|27|A|28|B|C]]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|29|8|@]|D|@$9|2A|A|2B|1|2C]]|E|$]]|$1|10|3|-4|5|6|7|2D|8|@]|D|@]|E|$]]]|11|$12|$5|13|14|15|E|$16|17|18|-4]]|19|$5|1A|14|1B|E|$1C|1D]]]]

Asp.Net Web API VS Asp.Net MVC
<a href="https://i.stack.imgur.com/B7FuD.png" rel="noreferrer"><img src="https://i.stack.imgur.com/B7FuD.png" alt="enter image description here"></a>
 1. Asp.Net MVC is used to create web applications that returns both
 views and data but Asp.Net Web API is used to create full blown HTTP
 services with easy and simple way that returns only data not view.

2. Web API helps to build REST-ful services over the .NET Framework and
 it also support content-negotiation(it's about deciding the best
 response format data that could be acceptable by the client. it
 could be JSON,XML,ATOM or other formatted data), self hosting which
 are not in MVC.

3. Web API also takes care of returning data in particular format like
 JSON,XML or any other based upon the Accept header in the request
 and you don't worry about that. MVC only return data in JSON format
 using JsonResult.

4. In Web API the request are mapped to the actions based on HTTP verbs
 but in MVC it is mapped to actions name.

5. Asp.Net Web API is new framework and part of the core ASP.NET
 framework. The model binding, filters, routing and others MVC
 features exist in Web API are different from MVC and exists in the
 new System.Web.Http assembly. In MVC, these featues exist with in
 System.Web.Mvc. Hence Web API can also be used with Asp.Net and as a
 stand alone service layer.

6. You can mix Web API and MVC controller in a single project to handle
 advanced AJAX requests which may return data in JSON, XML or any
 others format and building a full blown HTTP service. Typically,
 this will be called Web API self hosting.

7. When you have mixed MVC and Web API controller and you want to
 implement the authorization then you have to create two filters one
 for MVC and another for Web API since boths are different.

8. Moreover, Web API is light weight architecture and except the web
 application it can also be used with smart phone apps.

Original source is <a href="http://www.dotnettricks.com/learn/webapi/difference-between-aspnet-mvc-and-aspnet-web-api" rel="noreferrer">here</a>

blocks|key|2873178|text|HTML专注于使ASP.NET的输出变得简单。ASP.NET+Web+API专注于简化原始数据的输出。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2873179|在WebForms世界中，ASP.NET+MVC等同于.aspx页面，而ASP.NET+Web+API则是.asmx|2873180|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|$]]

ASP.NET MVC is focused on making output of HTML easy. ASP.NET Web API is focused on making output of raw data easy.

In the WebForms world, ASP.NET MVC would be equivalent to .aspx pages and ASP.NET Web API would be .asmx

blocks|key|3087047|text|HTTP用于创建同时返回视图和数据的web应用程序，而Asp.Net+Web+API用于创建完全成熟的Asp.Net服务，其方法简单，只返回数据而不返回视图。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3087048|Web有助于在.NET框架上构建REST-ful服务，它还支持内容协商(它是关于决定客户端可以接受的最佳响应格式数据。它可以是不在MVC中的JSON、XML、自托管。|3087049|Web+API还负责根据请求中的Accept头返回特定格式的数据，如JSON、XML或任何其他格式，您不必担心这一点。MVC使用JsonResult只返回JSON格式的数据。|3087050|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|$]]

Asp.Net MVC is used to create web applications that returns both views and data but Asp.Net Web API is used to create full blown HTTP services with easy and simple way that returns only data not view.

Web API helps to build REST-ful services over the .NET Framework and it also support content-negotiation(it's about deciding the best response format data that could be acceptable by the client. it could be JSON,XML, self hosting which are not in MVC.

Web API also takes care of returning data in particular format like JSON,XML or any other based upon the Accept header in the request and you don't worry about that. MVC only return data in JSON format using JsonResult.

With ASP.NET MVC controllers you can expose your data in different formats. AspNetWebAPI is designed explicitly for creating API's but I can easily do that with MVC controllers, is not clear to me in what cases it would be better than traditional MVC controllers. I'm interested in scenarios where the benefits of WebApi are obvious and it would be worthy to add another complexity layer to my applications.
Question: what are the advantages and/or disadvantages of using asp.net WebApi in respect to MVC ?

ASP.NET WebApi vs MVC?

路由

JSON

使用ASP.NET MVC控制器，您可以以不同的格式公开您的数据。AspNetWebAPI是专门为创建应用程序接口而设计的，但我可以很容易地用MVC控制器做到这一点，我不清楚在什么情况下它会比传统的MVC控制器更好。我对WebApi的好处显而易见的场景很感兴趣，并且值得在我的应用程序中添加另一个复杂性层。问题：使用as...

问ASP.NET WebApi vs MVC？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ASP.NET WebApi vs MVC？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ASP.NET WebApi vs MVC？
EN