I think that you are on the wrong path here. I would not at all wrap the ISession as I don't see what kind of issue you are trying to resolve.
IMHO it is better to wrap your query strategy in a seperate class in a seperation of concern kind of way. Then you can easily put optimizations in this class if needed and you can easily test this as well. On Mon, Aug 13, 2012 at 9:52 PM, Matteo Migliore <[email protected]>wrote: > Hi! > > I wrapped the ISession interface to an IRepository<T> (in a little more > complex way), now I've the problem to expose the eager loading feature > so I want to have this: > IRepository<T> : IEagerLoading<T> > ... > > IEagerLoading<T> : IQueryable<T> > { > IEagerLoading<T> Include<TRelated>(Expression<Func<T, TRelated>> path); > } > > On the IRepository<T> I want to write customerRepository.Include(x => > x.Addresses).Include(x => x.MainAddress); > > Do you know a simple way to do that? > > Thanks, > Matteo. > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/nhusers/-/030pE7I4fScJ. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > -- Ramon -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
