ASP.NET MVC 5 与 AngularJS/ASP.NET WebAPI [英] ASP.NET MVC 5 vs. AngularJS / ASP.NET WebAPI

问题描述

我目前正在评估用于在我的公司中创建未来 Web 应用程序的编程模型.所以我将在 ASP.NET MVC 5(带有 Razor 视图)和带有 ASP.NET WebAPI 的 AngularJS 之间做出决定.这两种编程模型的优缺点是什么?

I'm currently evaluating the programming model for creating future Webapplications in my company. So I will decide between ASP.NET MVC 5 (with Razor Views) and AngularJS with ASP.NET WebAPI. What are the advantages / disadvantages of these two programming models?

推荐答案

我的 2 美分.我个人更喜欢纯 HTML 视图，完全有角度的前端和 Web API/EF/SQL Server 后端，基本上没有 Razor.Razor 是一种帮助程序员呈现 HTML 的抽象，现在每个人都得出结论，删除这些抽象是一个更好的主意，因此 ASP.NET 从 Web 表单到 MVC 等的演变.开发人员并不难理解掌握 HTML 并使用有角度的前端，而且这使 UI 设计师的工作更轻松，他们拥有纯 HTML 和 JSON/Javascript，他们不需要去了解 MVC、Razor、控制器和动作.我们曾经完全在 MVC 上工作，在我们最新的项目中，我们转向了 Web API 后端和 Angular 前端，我们注意到 UI 设计师的工作效率得到了极大的提高.

My 2 cents. I personally prefer pure HTML views, an entirely angular front end along with a Web API/EF/SQL Server back end, basically no Razor. Razor is an abstraction to help programmers render HTML, these days everyone's coming to the conclusion that removing these abstractions is a better idea, hence the evolution of ASP.NET from web forms, to MVC etc. It's not really difficult for developers to get to grips with HTML and use an angular front end, moreover this makes UI designers jobs easier, they have pure HTML and JSON/Javascript, they don't need to go about understanding MVC, Razor, controllers and actions. We used to work completely on MVC, in our latest project we moved to a Web API back end and an angular front end, and we've noticed that our UI designer's productivity has vastly improved.

这篇关于ASP.NET MVC 5 与 AngularJS/ASP.NET WebAPI的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！