As nobody provided any realistic reason *not* to proceed as generally outlined, I suggest this proceed as planned taking into account the comments/suggestions made here (with the possible exception of the tangential thread about "make sure this works in VB.NET" ;)
-Steve B. On Feb 6, 8:39 am, Fabio Maulo <[email protected]> wrote: > Hi all. > I'm going to begin the implementation of "Loquacious mapping" in the trunk. > - API proposed in my blog (generics and strongly typed) > - *Mapper implementation as studied in ConfORM (namespaces ConfOrm.NH > and ConfOrm.Mappers ), neither generic nor strongly typed. > > Thoughts ? > > 2010/1/13 Fabio Maulo <[email protected]> > > > > > Hi team. > > > I would like to have a code re-view of my last post and > > a constructive feedback > >http://fabiomaulo.blogspot.com/2010/01/map-nhibernate-using-your-api.... > > > <http://fabiomaulo.blogspot.com/2010/01/map-nhibernate-using-your-api....>The > > post, and overall the code, is basically an example about how implement a > > custom API to create mappings by code. > > That is an invitation to everybody want create his own API and even an > > invitation for FNH team to use the Hbm* classes instead generate XML. > > > That said, seeing how things are going in each framework, NH needs its own > > mapping-by-code. > > Two matters here: > > 1) API definition > > 2) usage of Hbm* or directly create metadata (classes of namespace > > NHibernate.Mapping) > > > What is clear is that our implementation will supports anything supported > > by XML and, probably, we will improve some of actual > > "conventions-interceptors" (as, for instance, INamingStrategy & Co. ). > > > -- > > Fabio Maulo > > -- > Fabio Maulo
