Would you use the S#arp Architecture in a new commercial project?

Question

The S#arp Architecture seems really cool, but do you think it's still too new to make the commitment to it in an important new project? (Let's assume the project appears to be a good fit for it at first glance.)

It all seems very good, I'm just concerned that the new project I'm working on is using all the newer technologies - WCF, ASP.NET MVC etc - and that if I add one more infant technology I'm going to end up with lots of problems and not enough technical skill or community support to figure them out...

It's just so hard to resist that demanding boy inside me: I wanna have the newest stuff!

(Disclaimer: I'm very new to the S#arp Architecture, so I'm mostly basing my optimistic opinion of it on the stated goals of the project, articles, bits of sample code etc.)

Answer 1

http://fancydressoutfitters.co.uk was built using:

• Sharp Architecture (ASP.NET MVC, NHibernate, Fluent NHibernate),
• Spark View Engine
• AutoMapper
• NHibernate Validator
• xVal Validation Framework
• N2CMS
• PostSharp
• Solr & SolrNet

and it worked very well indeed. We documented a lot of our learnings from this project as blogs which you can find here: http://delicious.com/howardvanrooijen/fdo-casestudy

We also decided that we wanted to give back to the various Open Source Communities who helped us, so we created a new Sharp Architecture Showcase Application called Who Can Help Me? The source is available from http://whocanhelpme.codeplex.com and a live demo can be found at http://who-can-help.me