Sorry, I meant to say to make it virtual and not specify it in mapping. I thought that was implied, because we already told you that public properties had to be virtual.
Sounds like the other options are Make it virtual and don't map it (assuming this works like it does in fnh) Use fluent nh instead Make it private/protected internal and use public virtual functions What was the particular problem with making it virtual? I don't think you ever explained that. On Jun 5, 2014 7:08 AM, "Marco Giacinti" <marco.giaci...@gmail.com> wrote: > No Carl, if I do not code a property as virtual, I get the error *"An > invalid or incomplete configuration..."*. > I could try to go with *protected*, but this could give me headaches > using the code in different assemblies... > I was not able to find a way to tell NHibernate to "skip" this public > property.... > > -- > You received this message because you are subscribed to the Google Groups > "Fluent NHibernate" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to fluent-nhibernate+unsubscr...@googlegroups.com. > To post to this group, send email to fluent-nhibernate@googlegroups.com. > Visit this group at http://groups.google.com/group/fluent-nhibernate. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To unsubscribe from this group and stop receiving emails from it, send an email to fluent-nhibernate+unsubscr...@googlegroups.com. To post to this group, send email to fluent-nhibernate@googlegroups.com. Visit this group at http://groups.google.com/group/fluent-nhibernate. For more options, visit https://groups.google.com/d/optout.
