Pete,
Both option 2 & 3 seems to work, i just have to decide which one is less
evil. I am tempted towards 3, as, the parent most likely to be loaded
downstream anyway.
a
On Thursday, 12 September 2013 21:25:09 UTC+10, PeteA wrote:
>
> I understand the scenario, but not where the issue is; assuming that the
> C# looks like
>
> class Revision {
>
> public virtual Report { get; set; }
> }
>
>
>
> then this sounds like the correct behaviour. Are you attempting to do a
> typecast on the Report property? If so, that's not an ideal technique
> because of the proxy; there are a couple of things that can be done here:
>
>
>
> 1. (best if appropriate) - ensure that the common operations are all
> declared on the base class
>
> 2. (ugly and hacky but works) - add a property 'Self' to the base which
> returns 'this', then cast that instead
>
> 3. (not verified) - change the association from Revision --> Report to be
> non-lazy
>
>
>
> /Pete
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/nhusers.
For more options, visit https://groups.google.com/groups/opt_out.
