Just an observation,
List ancestors;
public virtual IList Ancestors
{
get
{
ancestors = ancestors ?? GetAncestors(this);
return ancestors;
}
}
This kind of properties will always be mapped with the current version
of FNH, because of the im
I'm not entirely sure what you're trying to do with that property, but
automapping has a ForTypesThatDeriveFrom method that you can call
IgnoreProperty inside, which is used to ignore specific properties.
On Wed, Mar 18, 2009 at 8:09 PM, wgp...@gmail.com wrote:
>
> Thanks John. I've decided to
Thanks John. I've decided to go back to writing the class mappings
myself until the automapping feature matures a bit. Decorating my
domain model with attributes for use only with the AutoPersistence
feature of FNH is in my opinion a violation of concerns.
On Mar 18, 10:26 am, Jon Kruger wrote
You have to put the attribute on the properties that you don't want to map
(if you're using the auto-mapper). The other alternative is to use the
fluent mappings for your class instead (that is, you write the mappings
instead of having the auto-mapper do it for you).
On Wed, Mar 18, 2009 at 1:22
Thanks. Does the last method in that thread simply not map unmappable
properties/methods ... or do I have to specify all the properties/
methods in each of my classes that I don't want mapped (seems like a
pain).
On Mar 18, 10:15 am, Jon Kruger wrote:
> This thread shows a couple different ways
This thread shows a couple different ways you can ignore properties
(unfortunately it's not baked into FNH):
http://groups.google.com/group/fluent-nhibernate/browse_thread/thread/3c338137374971ce
On Wed, Mar 18, 2009 at 1:12 PM, wgp...@gmail.com wrote:
>
> Example:
>
> I have a helper property
