They are all public and stuff, I just quickly wrote the snippet to demonstrate the names I was using. =) Thanks anyway! I'm not using fields, I'm using properties.
On Wed, Apr 28, 2010 at 4:52 PM, James Gregory <[email protected]> wrote: > Your classes and members need to be public. Fields aren't supported with the > automapper right now (though they will be before the next release). > > On Wed, Apr 28, 2010 at 9:28 PM, Henrique Cabral <[email protected]> wrote: >> >> I will give it a try. Both sides of the relationships and naming have >> followed the conventions, using plurals for the name of lists. In my >> case: >> >> class Owner >> { >> IList<Security> Securities >> } >> >> class Security >> { >> IList<Owner> Owners >> } >> >> And of course, all the constructors, database tables, etc. Still, FNH >> didn't seem to find the tables. No exceptions were thrown as well. >> Maybe if I use a concrete List or IEnumerable? >> >> Thanks! >> Henrique >> >> -- >> 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. >> > > -- > 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. > -- 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.
