unity-container

Take the following useless program: class Program { static void Main(string[] args) { IUnityContainer unityContainer = new UnityContainer(); IWindsorContainer windsorContainer = new WindsorContainer(); Program unityProgram = unityContainer.Resolve<Program>(); Program castleProgram = windsorContainer.Resolve<Program>(); } } The UnityContainer will return me an instance of Program, where as the Windsor container will throw a ComponentNotFoundException. I can see arguments for both behaviours and don't mind which I end up with, however Prism V2 Drop 8 (the latest at time of writing) relies on the

I'm using Unity successfully for all regular constructor injection such as repositories etc., but I can't get it working with the ASP.NET Identity classes. The setup is this: public class AccountController : ApiController { private UserManager<ApplicationUser> _userManager { get; set; } public AccountController(UserManager<ApplicationUser> userManager) { if (userManager == null) { throw new ArgumentNullException("userManager"); } _userManager = userManager; } // ... } with these configs for Unity: unity.RegisterType<AccountController>(); unity.RegisterType<UserManager<ApplicationUser>>(new

This helpful article from David Haydn (EDIT: scam link removed, it could have been this article ) shows how you can use the InjectionConstructor class to help you set up a chain using the decorator pattern with Unity. However, if the items in your decorator chain have other parameters in their constructor, the InjectionConstructor must explicitly declare each one of them (or Unity will complain that it can't find the right constructor). This means that you can't simply add new constructor parameters to items in the decorator chain without also updating your Unity configuration code. Here's