S#arp Architecture (Pronounced “Sharp Architecture”) this is a solid architectural foundation for rapidly building maintainable web applications leveraging the ASP.NET MVC Framework with NHibernate. The primary advantage to be sought in using any architectural framework is to decrease the code one has to write while increasing the quality of the end product. A framework should enable developers to spend little time on infrastructure details while allowing them to focus their attentions on the domain and user experience.
Billy McCafferty has released the new version of the Sharp Architecture.
It has been a while since the last release and the development team have had some nice features added. The biggest items in this release are:
- Fluent NHibernate 1.1 – We are now using version 184.108.40.2065. The AutoMappingPersistenceGenerator has been updated to use the new bits as well.
- NHibernate Configuration caching has now been added.
- CRUD forms now enable client side validation
This release was almost 100% done by the community, that is amazing! The author would like to thank everyone who contributed to this release in his blogpost. “I truly appreciate your help and feel that it benefits the community greatly” – he also said.
S#arp Architecture review
S#arp Architecture adheres to the following key principles:
- Focused on Domain Driven Design
- Loosely coupled
- Preconfigured Infrastructure
- Open Ended Presentation
The overall goal of this is to allow developers to worry less about application “plumbing” and to spend most of their time on adding value for the client by focusing on the business logic and developing a rich user experience.
More information available on a Sharp Wiki.
Next for Sharp Architecture
1.6 will be the last version to support VS 2008 as well as .NET 3.5. The team will keep a branch available for the community to maintain, but no further development will be done against this branch. The next version will be tagged 2.0, support only VS 2010 and .NET 4.0.
At the moment team focused on increasing code coverage and creating better documentation.
Waiting for new releases. Good luck and Thanks.