Wow. Amazing diagram. I'll have a better look at the HBM* POCOs, but if they differ from the xml at all, then I'll probably stick with the XSD generated library - most of us are au fait with the XSD, so it's helpful if the API matches the XSD.
Of course thats not really my main point. My main point is that you can roll your own automappings very easily using L2XSD or HBM* - see part 2 for details! On Jul 15, 6:55 pm, José F. Romaniello <[email protected]> wrote: > Very interesting, although you should read > this:http://fabiomaulo.blogspot.com/2010/03/nhibernate-mappings-path.html > > <http://fabiomaulo.blogspot.com/2010/03/nhibernate-mappings-path.html>You > don't need XSD to .Net conversion, because this is already in nhibernate; > the "HBM*" classes.. those are simple POCO's. > > have a look to conform: > > http://code.google.com/p/codeconform > > 2010/7/15 mcintyre321 <[email protected]> > > > > > Sorry for the self promotion - I'm writing a series on how I do NH > > mappings and thought it might be of interest to some. The first post > > is here, the second is soon to follow. > > >http://www.adverseconditionals.com/2010/07/fluent-xml-free-convention... > > > -- > > You received this message because you are subscribed to the Google Groups > > "nhusers" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<nhusers%[email protected] > > > > > . > > For more options, visit this group at > >http://groups.google.com/group/nhusers?hl=en. -- You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en.
