views:

675

answers:

2

What's the best ASP.NET MVC based blog engine out there which is ready to deploy? I am guessing there are no MVC blog engines which are comparable with WebForms based blog engines like dasBlog, BlogEngine and subText? I think Oxite is a dead end and Orchid is more like a CMS.

Looking for an engine which can do these:

  • RSS feeds support

  • anti comment spam functionality like support for Akismet

  • comment post approval support

  • Some kind of theming if possible

+3  A: 

The research I've done indicates there are very few. Zero if you take out Oxite and Orchid.

For what it's worth, I'm writing one right now and plan on releasing it as Open Source once it is releaseable.

The goal is to have it be easily installable and have the feel of Stack Overflow's Question asking and voting mechanism experience, using Markdown as the editor.

Phil haack has also talked about rewriting subText in ASP.NET MVC.

To answer @Zowen's comment on the WebFormViewEngine. The Book ASP.NET MVC 1.0 by Scott Hanselman et. al., says:

As we tend to reiterate in this chapter, WebFormViewEngine is a bit of a misnomer. We had intense debates on what to name this default View engine. We considered DefaultViewEngine, but as you saw earlier, it's not really the default; AutoViewEngine is. Also the name is not very descriptive.

We considered PageViewEngine, or even AspxViewEngine, but then what about partial Views, which are implemented as user controls? Phil [Haack] tried to put forth TemplateControlViewEngine because the one thing that Page, UserControl, and MasterPage all share in common is that they derive from TemplateControl. That was rejected because that name was obsure, as the connection to TemplateControl is not readily apparent or well known.

In the end, we stuck with WebFormViewEngine because we never really came up with a better name and we deemed it good enough. Rob's [Conery] sure that, upon reading this aside, someone will come up with the perfect name and we will end up regretting the name we chose. -- From ASP.NET MVC 1.0, Page 270.

George Stocker
At the moment, SubText trunk builds are MVC/webforms hybrid. If I were writing a blogging engine, I would give that a serious look.
zowens
@zowens Why? I have no desire to support webforms.
George Stocker
It's hybrid because it's being converted from WebForms to MVC. Actually it could be a good exercise for WebForms developers trying to learn MVC, myself included. That's the reason I was looking for an MVC blog engine so that I can use it and learn MVC at the same time.
Tony_Henrich
@george-stocker MVC is built on webforms. You're supporting webforms anyways if you use the default view engine. That's pretty much a reality.
zowens
@zowens See my edit above. ASP.NET MVC is not built on webforms. It's built on the .NET Framework, but it doesn't use the webforms methodology.
George Stocker
@george-stocker I am very much aware of that. But "webforms" is the default view engine. It has a page (ViewPage base class). The default view engine technically IS webforms.
zowens
A: 

I know this is an old post but I found this MVC engine:

http://blogsvc.codeplex.com/

It looks simpler than Orchard which is a good thing.

rboarman