I've seen Mike's implementation before and it has the same issues. Notice his repository takes an IDataContextProvider. He probably has a concrete class that just returns a single data context instance, whereas I support multiple data context types in the same application.
I think it's clear at this point that there's no built in way to handle the scenario I need. Thanks for all the help. On Mar 7, 2:25 pm, José F. Romaniello <[email protected]> wrote: > 2011/3/7 Rob <[email protected]> > > > It's hard for me to separate out and I don't have the rights to paste > > it directly. > > Then, you can ask the person who own the rights how to refactorize it. > > Are you aware of any other repository pattern implementation > > > techniques for linq to sql? > > I've never used Linq To Sql but the first google search return a meaningful > implementation:http://mikehadlow.blogspot.com/2008/03/using-irepository-pattern-with... > IRepository<T> implemented by Repository<T> > BTW; guess what, it seems to be free! > > To register this class the only thing you need to do is: > > Container.Register(Component.For(typeof(IRepository<>)).ImplementedBy(typeo > f(Repository<>)); > as i told you in one of my mails. -- You received this message because you are subscribed to the Google Groups "Castle Project Users" 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/castle-project-users?hl=en.
