btw Michael, The CompileMappingsForEachExplicitlyAddedEntity i mostly for those ppl who like to do everything class-by-class. As you saw the transition between convention-base and polymorphic mapping is very short in NH3.2 and that method is not the best to use. In fact, your case, you can create the mapping for a class even when its explicit mapping-declaration does not exists at all (you have mapped just the interface).
On Fri, Apr 29, 2011 at 9:42 AM, Fabio Maulo <[email protected]> wrote: > Yes it was ;) (already fixed few days ago in the trunk). > > > On Fri, Apr 29, 2011 at 9:30 AM, Michael DELVA <[email protected]>wrote: > >> If you wish me to send you the example, I can, no problem. >> >> But what I need is already in the code I posted before. >> >> Tell me if it's OK for you. >> >> BTW, I have a question: >> >> I use the ModelMapper. If I have 15 classes which implement IStatistic, to >> make all work I have to call mapper.SubClass<>() for each of the 15 classes, >> and add the 15 types to the method mapper.CompileMappingFor(). >> >> If I replace the CompileMappingFor by >> CompileMappingsForEachExplicitlyAddedEntity, then the subclasses are not >> added to the mapping. >> >> Is this a bug? >> >> Thanks in advance >> >> -- >> 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. >> > > > > -- > Fabio Maulo > > -- Fabio Maulo -- 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.
