Hi!

I've wrapped a LINQ to SQL model twice, and using it in an ADO Data
Services service gives me a lot of trouble trying to expand the
associations. All I get is a <link rel="self" href="..."/> entry.
I've tried to add numerous [IgnoreProperties] attributes to make the
objects as slim as possible when debugging, but I can't figure out why
it don't work. LoadProperty works as expected, so it obviously
understands the associations.

Anyone have any ideas why this is?

L-E

On 14 Okt, 15:30, Lars-Erik <l...@markedspartner.no> wrote:
> Hi!
>
> I've wrapped a LINQ to SQL model twice, and using it in an ADO Data
> Services service gives me a lot of trouble trying to expand the
> associations. All I get is a <link rel="self" href="..."/> entry.
> I've tried to add numerous [IgnoreProperties] attributes to make the
> objects as slim as possible when debugging, but I can't figure out why
> it don't work. LoadProperty works as expected, so it obviously
> understands the associations.
>
> Anyone have any ideas why this is?
>
> L-E

Man I feel stupid. :P I've been spending two days finding my own
architectural grip where the wrapped context I use presets a few
dataloadoptions, not including the one I want now. An eager-load
dataload option on the innermost context, et voilá - I'm there!

L-E