This is the age old question - bespoke vs off the shelf.
With Umbraco you have the potential for an awful lot more site in a lot less time since the requirement is substantially to produce the content rather than the infrastructure. In terms of UI you can produce you should be pretty close either way - Umbraco gives you a lot of control.
With MVC you get to do anything you want - but one way or another you have to build it and, more importantly in terms of this question, you have to build the tools to maintain the content too.
And this is why there is a dilemma - because with Umbraco (or any packaged CMS) the question is 1) can you do what you need within its constraints and 2) where you can't how easy is it to extend the system to deal with those elements that need to be custom.
Finally there's the question of who is maintaining the content - if its to be the site "owner" (which it should be) how are they going to interact with the system? This is the advantage that Umbraco has in that the whole content maintenance thing is handed to you on a plate.
One last point - remember that you have a duty to your client to choose what is best for them and not to choose a platform because you want to play with new toys. Thankfully a lot of the time the two coincide (-: but its worth bearing in mind. (Oh, and before you write off forms completely, remember that ASP.NET Dynamic Data - forms based - will give you an instant database maintenance site which will go some way toward dealing with the maint problem that you'd have with an MVC site).
So... no absolute answer because there is no single "right" - you're almost always working on a case by case basis.
比较 MVC 和 Umbraco 实际上就是比较苹果和橘子。 Umbraco 是一个内容管理系统，因此提供了客户所需的大量开箱即用功能，而 MVC 是一个 Web 开发框架，因此处于比 Umbraco 更低的级别。使用 MVC 实现客户端所需的功能与使用 ASP.NET Web 表单实现完全相同的功能非常相似。事实上，Umbraco 可能会在某一时刻决定使用 MVC 来实现其功能。
因此，我同意 Murph 的观点，选择应该是内容管理系统，而不是使用 MVC 或任何其他 Web 开发框架自行实现 CMS 功能（是的，MVC 非常棒）。
Comparing MVC and Umbraco is comparing apples and oranges really. Umbraco is a Content Management System and as such provides plenty of out of the box functionality that it seems your client needs, whereas MVC is a web development framework, and as such is at a lower level than Umbraco. Using MVC to implement the features needed by your client is very much the same as using asp.net web forms to implement the very same features. In fact, Umbraco could decide at one point to use MVC to implement it's features.
So I agree with Murph, the choice should be Content Management System versus implementing CMS features yourself using MVC or any other web development framework (and yes, MVC is brilliant).
Since you are familiar with Umbraco, as am I, you know that you will be stuck integrating packages. This may not be a bad thing, but it is a consideration. You will not be able to use that website with any other solution. As you know Umbraco consumes the entire website.
I personally would go with MVC, because I love it. Version 2 was just released today, making it even easy to put an application together in no time.
发布评论
评论（4）
这是一个古老的问题——定制与现成的。
有了 Umbraco，您就有可能在更少的时间内创建更多的网站，因为需求基本上是生成内容而不是基础设施。就用户界面而言，无论哪种方式，你都应该非常接近 - Umbraco 为你提供了很多控制权。
使用 MVC，您可以做任何您想做的事情 - 但您必须以某种方式构建它，更重要的是，就这个问题而言，您还必须构建工具来维护内容。
这就是为什么会出现困境 - 因为使用 Umbraco（或任何打包的 CMS），问题是 1) 您能否在其限制内完成您需要的操作，以及 2) 您不能的情况下扩展系统来处理问题有多容易以及那些需要自定义的元素。
最后还有一个问题，即谁在维护内容 - 如果它是网站“所有者”（应该是），他们将如何与系统交互？这就是 Umbraco 的优势，因为整个内容维护的事情都交给你了。
最后一点 - 请记住，您对客户有责任选择最适合他们的东西，而不是因为您想玩新玩具而选择平台。值得庆幸的是，很多时候两者是一致的（-：但值得牢记。（哦，在您完全注销表单之前，请记住 ASP.NET 动态数据 - 基于表单 - 将为您提供一个即时数据库维护站点，该站点将在某种程度上解决您在 MVC 站点中遇到的维护问题）
所以...没有绝对的答案，因为没有单一的“正确” - 您几乎总是根据具体情况进行工作。
This is the age old question - bespoke vs off the shelf.
With Umbraco you have the potential for an awful lot more site in a lot less time since the requirement is substantially to produce the content rather than the infrastructure. In terms of UI you can produce you should be pretty close either way - Umbraco gives you a lot of control.
With MVC you get to do anything you want - but one way or another you have to build it and, more importantly in terms of this question, you have to build the tools to maintain the content too.
And this is why there is a dilemma - because with Umbraco (or any packaged CMS) the question is 1) can you do what you need within its constraints and 2) where you can't how easy is it to extend the system to deal with those elements that need to be custom.
Finally there's the question of who is maintaining the content - if its to be the site "owner" (which it should be) how are they going to interact with the system? This is the advantage that Umbraco has in that the whole content maintenance thing is handed to you on a plate.
One last point - remember that you have a duty to your client to choose what is best for them and not to choose a platform because you want to play with new toys. Thankfully a lot of the time the two coincide (-: but its worth bearing in mind. (Oh, and before you write off forms completely, remember that ASP.NET Dynamic Data - forms based - will give you an instant database maintenance site which will go some way toward dealing with the maint problem that you'd have with an MVC site).
So... no absolute answer because there is no single "right" - you're almost always working on a case by case basis.
比较 MVC 和 Umbraco 实际上就是比较苹果和橘子。 Umbraco 是一个内容管理系统，因此提供了客户所需的大量开箱即用功能，而 MVC 是一个 Web 开发框架，因此处于比 Umbraco 更低的级别。使用 MVC 实现客户端所需的功能与使用 ASP.NET Web 表单实现完全相同的功能非常相似。事实上，Umbraco 可能会在某一时刻决定使用 MVC 来实现其功能。
因此，我同意 Murph 的观点，选择应该是内容管理系统，而不是使用 MVC 或任何其他 Web 开发框架自行实现 CMS 功能（是的，MVC 非常棒）。
Comparing MVC and Umbraco is comparing apples and oranges really. Umbraco is a Content Management System and as such provides plenty of out of the box functionality that it seems your client needs, whereas MVC is a web development framework, and as such is at a lower level than Umbraco. Using MVC to implement the features needed by your client is very much the same as using asp.net web forms to implement the very same features. In fact, Umbraco could decide at one point to use MVC to implement it's features.
So I agree with Murph, the choice should be Content Management System versus implementing CMS features yourself using MVC or any other web development framework (and yes, MVC is brilliant).
由于您和我一样熟悉 Umbraco，因此您知道您将陷入集成软件包的困境。这也许不是坏事，但也是一个考虑因素。您将无法通过任何其他解决方案使用该网站。如您所知，Umbraco 占用了整个网站。
我个人会选择 MVC，因为我喜欢它。第 2 版今天刚刚发布，让您可以轻松地立即构建应用程序。
Since you are familiar with Umbraco, as am I, you know that you will be stuck integrating packages. This may not be a bad thing, but it is a consideration. You will not be able to use that website with any other solution. As you know Umbraco consumes the entire website.
I personally would go with MVC, because I love it. Version 2 was just released today, making it even easy to put an application together in no time.
只是想告诉你我正在走n2 + mvc 道路。
感谢您的回答！
Just want to tell you that I'm going down the n2 + mvc road.
Thanks for the answers!