Oxite or S#arp Architecture for new Asp.net CMS site

Question

I'd like to build a CMS site based on Asp.Net Mvc and I want to choose my starting point.

I have seen that there is a lot of interest in the new Microsoft Oxite project also if it seems to be pretty early to adopt it in a production project.
I've also looked at S#arp Architecture but it does not properly compare to Oxite as is just a starting point for general Asp.Net Mvc sites.

For me S#arp Architecture has some advantages over Oxite as is far less complex and it uses Nhibernate for the data access layer.
Oxite code uses Linq2Sql for it's DAL and has already a project in the solution that requires the DB version for VS2008.
Oxite seems to me more blog oriented than CMS oriented but I haven’t looked the code deeply.

Here are some of the choices that would point me to S#arp Ar. for starting.

• Simple clean architecture
• Nhibernate Dal
• Community supported

Oxite:

• Microsoft project
• Potential huge community
• Early stages but very good code quality
• Provider model that permits to easily switch the DAL

If anyone has looked at the code of these two projects please advice on your opinions.

Thanks

Answer 1

Oxite might be feature rich, but the code quality is very low.

I was very surprised when I checkout the code and found controller actions with 100+ lines of very unclean code, tagsoup views, no unit tests, etc.

The criticism has been well summed up in these blog posts:

http://blog.wekeroad.com/blog/some-thoughts-on-oxite/

http://codebetter.com/blogs/karlseguin/archive/2008/12/15/oxite-oh-dear-lord-why.aspx