Is Orchard or Umbraco MVC?

I'm much happier with the quality of outp开发者_如何学Pythonut I can get with MVC over webforms: hand crafted HTML that isn't full of additional machine generated gubbins (polite term). I realize of course that MVC is about a lot more than this, but concentrating on just that "view" part...

I'm looking at Orchard or Umbraco for a project. I see both support Razor syntax (Umbraco just about) - but with my strong leaning to MVC Views rather than webforms, does that rule out Umbraco?

All the Umbraco reading I've found so far is about the XSLT engine, as the razor syntax is brand new, which scares me :-)

Orchard runs on ASP.NET MVC - it was designed like that from the very beginning. Building apps with it is much like building ordinary ASP.NET MVC 3 application, so the learning curve is not that steep. Also Orchard delivers an extensible component framework to ease building MVC apps, so I guess it's much more than a CMS. And at it's core it uses pure MVC approach (fully controllable and no trash markup attached) to render final output.

Don't know much about Umbraco, though. Tried that some time ago and at first sight it just looked overcomplicated, so I searched for other solution and sticked to Orchard as it appeared pure and simple. It was over a year ago, so at that time Orchard was in pretty early stage (<0.5), not ready for production use, though. But lots have changed since then and now it's a full-featured platform with large community behind it. Not to add that Orchard is free, open-source and has a strong Microsoft support (financial and personal). The team working on it is all ASP.NET guys, so I guess it can't be better:) Btw - the newest Orchard release - 1.1 - will be officially announced on upcoming MIX'11.

I'm currently building two large commercial applications based on Orchard and I'm just very happy with it.

Umbraco 4.7 does not yet use MVC, but you have total control over the HTML output. Razor syntax is supported, for most tasks you won't be needing XSLT anymore.

Orchard is based on MVC, but it's also more than only a CMS. The focus is on developing reusable components.

In my opinion, the most important point whether to go with Umbraco or Orchard is maturity: Umbraco is stable and mature, with a big and very friendly community (which makes up for the slight lack of documentation of the latest features). Orchard's first version was released only recently. Therefore, I'd definitely go right now with Umbraco, but keep an eye on Orchard - there's certainly a lot to learn from this project.

Just a quick update on umbraco, as of 13th June 2012, umbraco has ceased development on V5.

They are focusing on a better 4.x with the move to MVC coming but not yet.

As far as I am aware razor support will continue.

Umbraco v5 (currently RC1 10 Jan 2012) is a ground up rewrite in MVC. It changes the answer to this (9 month old) question.

We use Umbraco for over a year, they just release 4.7 in witch you can use Razor and it's great! But if you want to build custom usercontrol in Umbraco you have to go webforms way, but since Umbraco it's a CMS for developper, you can almost do anything without having to build usercontrol. This summer Umbraco 5.0 will be release and it will be using MVC, I guess they will rule the CMS world after that ;)

Don't know about Orchard, I was having the same question one year ago and read about Orchard and it does not seems so nice for what I saw.

Anyway, hope my umbraco experience help you take your decision, let me know if you have more question.

My take to this whole topic and including the "DOA" Umbraco 5 is that people are afraid of change, Umbraco 5 to me was by far the best CMS in both Razor syntax and MVC platform, everything was simplified. I mean from creating templates to managing content both static and dynamic content. I'm still gonna keep my umbraco 5, work on it locally with the high hopes of it coming back very soon.

I've been using Umbraco since version 7.1.4 and I've always used MVC with it. I know there is still support for web forms too, but its main direction is down the MVC route. The current version as I write this comment is 7.6.3