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

问题描述

我目前正在评估用于在公司中创建未来Web应用程序的编程模型.因此，我将在ASP.NET MVC 5(带有Razor Views)和带有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后端和有角度的前端，并且我们注意到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屋！