This would be nice to have! My vote for this.
On Tue, Sep 10, 2013 at 12:07 PM, Dmitry Naumov <[email protected]>wrote: > There are multiple places in NHibernate where custom types may be provided > like connection provider, cache etc. The problem is that these instances > are created through reflection, leaving possibly existing application IoC > container out of play. Why not to go the same way as ASP.NET or WebApi > went? > > We can extend NHibernate.Cfg.Configuration with DependencyResolver > property. Default out-of-the-box implementation of Resolve method will use > same reflection code as it now does. But it can be substitute by "real" IoC > container adapter, so application developer will avoid creating singletons > and service locators just to connect custom NHibernate-specific types with > other application types and services. > > -- > > --- > You received this message because you are subscribed to the Google Groups > "nhibernate-development" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
