Miha, I am also using FNH automapping in my project, and have a similar requirement to map multiple ILists of the same type in some of my classes.
Following advice from the FNH mailing list, I ended up with a solution almost identical to yours, a base class (though it's not defined as Abstract), and a derived class for each IList that is a member of the same class. This Automaps perfectly well _as is_ - no overrides, no where clauses, no mapping files are needed. I see you are using ISets, not ILists, and am not sure if Automapping supports ISets. But I know this approach works very well with ILists. The other difference I see is that you are using private backing variables for your ISets. This is a fairly recent addition to FNH Automapping that was not available to me several months ago when I started my project. >Again: it works for saving, but does not work for loading entities. What happens when you load? -Tom Bushell -- 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.
