Would you use the S#arp Architecture in a new comm

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

I don't see S#arp Architecture as a framework or even an "architecture" but an awesome starting point for developing an application using MVC and Fluent NHibernate. The project and files are well organised based on the Visual Studio template it provides. That by itself is worth a ton to get one up and running fast. I suggest looking over the Northwind sample source that comes with the source of S#arp Architecture to see what's possible.