Recently I was wondering how PRISM (Composite Application Guidance for WPF & Silverlight) achieved a magic trick with its dependency injection (DI) container. I knew in PRISM you are free to swop in your own DI container, which is nice but I was wondering how you achieved the trick of having your container available within itself. What do I mean? Put simple being able to resolve your DI Container in any class within your application. Example: Where ‘Foo’ is just a plain old class within the applicati...
|
2
shouts |
|
|||
No comments yet, be the first one to post comment.