Yeah, good point by Chris. Fluent NHibernate doesn't have to be an all-or-nothing affair, you can replace your entities bit-by-bit with FNH and it'll be happy; it might also be worth considering just writing new mappings with FNH until everyone is familiar enough with it to port the rest of your mappings.
On Wed, Feb 4, 2009 at 3:02 PM, Chris Marisic <[email protected]> wrote: > > Also don't forget you can use any combination of HBM, Mapping and > Automapping! > > On Feb 3, 10:13 pm, bbehrens <[email protected]> wrote: > > I was wondering if any of the project owners would like to have a > > ClassMap<T> generator. The idea is you take existing .hbm files and > > it creates the ClassMaps for you. Exactly like you can go from > > ClassMap files to .hbm files. > > > > I've been looking hard at FNH for the past week or so. I showed it to > > one of my team members and his first response was "you mean we'd have > > to go through that mapping process again?" I thought about it figured > > one of the major benefits of FNH is you can get away from the mapping > > files. Why not make the barrier of entry less painful for people > > wanting to go with FNH over traditional .hbm mapping files? > > > > I'm going to write some a patch for our internal use that will do > > that. I would be happy to contribute the code to the project if there > > is any interest. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/fluent-nhibernate?hl=en -~----------~----~----~----~------~----~------~--~---
