NHibernate

S#arp Architecture

Diego Lazzarino — Thu, 16 Apr 2009 10:54:59 GMT

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. Accordingly, 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.

Good background material reading includes http://www.codeproject.com/KB/architecture/NHibernateBestPractices.aspx. Although there are major infrastructural changes from this article in the current architecture, the general structure is very similar and the background reading is very helpful in understanding many of the ideas behind this architecture. S#arp Architecture documentation is included along side the current release.

S#arp Architecture and the preceding article have been referenced in NHibernate in Action by Pierre Henri Kuate, Windows Developer Power Tools by James Avery and Pro LINQ Object Relational Mapping in C# 2008 by Vijay P. Mehta.

Billy McCafferty

Project homepage

Summer of NHibernate Screencast Series

Diego Lazzarino — Fri, 03 Oct 2008 12:55:08 GMT

Interessante serie di screencast su NHibernate

http://www.summerofnhibernate.com/

Diego

NHibernate ResultTransformer

Diego Lazzarino — Fri, 11 Apr 2008 10:47:36 GMT

Problema
Trasformare un resultset generico in una lista tipizzata di DTO (quindi non una entity del Domain Model).

Soluzione
Utilizzare ResultTransformer di NHibernate.
Quest'interfaccia consente di specificare una classe di output sulla quale verrà "mappatio" il resultset.

Esempio

File di mapping

    <sql-query name="GetCashFlowMainData">
        
        <return-scalar column="Id" type="Int32" />
        <return-scalar column="ReportType" type="Int32" />
        <return-scalar column="RepGroup1" type="Int32" />
        <return-scalar column="RepGroup2" type="Int32" />
        .......  
 

Snippet codice

IQuery query = ((IUnitOfWorkExtended)UnitOfWork).GetNamedQuery("GetCashFlowMainData");
 
query.SetInt32("IdReport", idReport);
query.SetInt32("DayFrequency", dayFrequency);
query.SetDateTime("StartDate", startDate);
query.SetInt32("PeriodNumber", periodNumber);
 
query.SetResultTransformer(Transformers.AliasToBean(typeof (CFRptCashFlowDTO)));
 
IList<ICFRptCashFlowDTO> result = quey.List<ICFRptCashFlowDTO>();
     

Diego

NHibernate Mapping: verificare lo schema del database

Diego Lazzarino — Thu, 03 Apr 2008 18:17:32 GMT

Snippet per verificare che lo schema del database corrisponda a quello descritto dal nostro Domain Model.

[Test]

public void AllNHibernateMappingAreOkay()

{

ISessionManager sessionManager = IoC.Resolve<ISessionManager>();

using (ISession session = sessionManager.OpenSession())

{

IDictionary allClassMetadata = session.SessionFactory.GetAllClassMetadata();

foreach (DictionaryEntry entry in allClassMetadata)

{

session.CreateCriteria((Type) entry.Key)

.SetMaxResults(0).List();

}

Fonte Ayende