Basically, you are going to have to do the loading yourself. I actually
brought this up with the PM for LINQ-to-SQL at MS, indicating that I don't
want to have to do all of the loading myself, because as the type hierarchy
grows, so do the number of calls I need to place in other places to load the
hierarchy.
I think that you could probably create a reflection-based routine
(assuming you don't have any strong base types which represent related
records) which will access the properties which expose other entities and
therefore, load them.

Signature
- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard.caspershouse.com
> sorry i was too happy to find something those are about prefetching
> and loadingOptions
[quoted text clipped - 3 lines]
> fetch the data, this after populating my list and releasing my context
> object.
fredd00 - 10 Jan 2008 18:48 GMT
On Jan 10, 11:28 am, "Nicholas Paldino [.NET/C# MVP]"
<m...@spam.guard.caspershouse.com> wrote:
> Basically, you are going to have to do the loading yourself. I actually
> brought this up with the PM for LINQ-to-SQL at MS, indicating that I don't
[quoted text clipped - 18 lines]
> > fetch the data, this after populating my list and releasing my context
> > object.
Hi
thanks for the reply,
so the short answer is there is no real lazy loading if the context is
closed
i would need to implement it in the property
open a new context get the data a maintain it i my object
i don't see why microsoft did not do the extra step , it's not such a
big job but would have been a real implementation of lazy loading
thanks again
Nicholas Paldino [.NET/C# MVP] - 10 Jan 2008 20:32 GMT
BTW, it should be mentioned that what you want to do isn't really lazy
loading, it's really up-front loading.

Signature
- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard.caspershouse.com
> On Jan 10, 11:28 am, "Nicholas Paldino [.NET/C# MVP]"
> <m...@spam.guard.caspershouse.com> wrote:
[quoted text clipped - 38 lines]
>
> thanks again
fredd00 - 11 Jan 2008 14:48 GMT
On Jan 10, 3:32 pm, "Nicholas Paldino [.NET/C# MVP]"
<m...@spam.guard.caspershouse.com> wrote:
> BTW, it should be mentioned that what you want to do isn't really lazy
> loading, it's really up-front loading.
[quoted text clipped - 49 lines]
>
> > thanks again
you are right in this exemple i should use up-front loading of the
child, which i am now doing
but for some other situation i might want to use lazy loading , and I
wanted to know if it was possible.
Seems like it's not possible unless I code it myself
thanks