i did solve my problem a little bit different (but i think its ok)

make your Resolver-TYpe to be singleton (static class e.g.) and register mapping in application start event of global.asax

Your CORE library would be loaded during the bootup in the context of web application and therefore it would be able to retreive IRepository service

HTH,

Nikola

this article and the series of DI articles are very good written (esp. the samples are perfect).

may i ask you a question regarding the implementation: in my project, i have a class-lib-project (CORE) where there are a lot of repositories and manager classes. i have on Resolver-Type, and if i need some sort of repository, i call Resolver.Resolve<T> …  (it s a little bit like your facade.resolver).

this all works well.

now i have a web-project, this instantiates the repository/manager classes of CORE. therefore this project also needs a DI container.

this also works well.

now, i wanted to reduce type-creations, so e.g. the user-repository should only be created one time. so i choosed to type it as singleton (with unity).

but, because CORE instantiates a container, and web instantiates a container, i have two instances of that particular repository.

what is your tipp to solve this part of my problem?

here it is: the proof of how stupid copy- paste driven development can be

I’ve updated the source code and blog post

Thanks for the tip!

# public UserManagerSL(): this (ServiceLocator.Retrieve<IUserProvider>())  

#         {  

#             this.userProvider = userProvider;  

#         }

There’s no userProvider argument, and in fact you don’t need a body for this constructor anyway, since you’re calling the other constructor with this(…)