Windsor currently does not support that, and it’s by design. The reasoning is that you should explicitly register types you need so that you dont get misconfigured object. There is however a possibility that there will be added a hook to create non-registered type at some point in the near future, as this is needed … Read more
So after some research I came up with the following solutions to my problems: Use Unity with ASP To be able to use Unity with ASP I needed a custom IServiceProvider (ASP Documentation) so I wrote a wrapper for the IUnityContainer which looks like this public class UnityServiceProvider : IServiceProvider { private IUnityContainer _container; public … Read more
Neat solution, but each instance of LifetimeManager should use a unique key rather than a constant: private string _key = string.Format(“PerCallContextLifeTimeManager_{0}”, Guid.NewGuid()); Otherwise if you have more than one object registered with PerCallContextLifeTimeManager, they’re sharing the same key to access CallContext, and you won’t get your expected object back. Also worth implementing RemoveValue to ensure … Read more
I have moved away from using PerRequestLifetimeManager for this very issue. I have now started using HierarchicalLifetimeManager with container hierarchies instead and then you need to set up your app to create a new child container per intended scope (such as a request or a job) and dispose that child container when that scope is … Read more
This problem arises with older version of nuget. Update nuget PM, 2.8.50313.46 is current version, Look for the latest for VS 2012
First, you need a proper lifetime manager the ContainerControlledLifetimeManager is for singletons. For custom initialization, you could probably use InjectionFactory This lets you write any code which initializes the entity. Edit1: this should help public static void Register(IUnityContainer container) { container .RegisterType<IEmail, Email>( new ContainerControlledLifetimeManager(), new InjectionFactory(c => new Email( “To Name”, “[email protected]”))); } and … Read more
Just for others (like me) who might have faced the above error. The solution in simple terms. You might have missed to register your Interface and class (which implements that inteface) registration in your code. e.g if the error is “The current type, xyznamespace. Imyinterfacename, is an interface and cannot be constructed. Are you missing … Read more
You also need to resolve the UserManager. The following is an example how you could do it with the UserManager and the RoleManager. In this sample I use the regular Unity 3 package instead of one of the derivates or bootstrappers (had some problems with them in the past). AccountController private readonly UserManager<ApplicationUser> _userManager; private … Read more
Another approach, thanks to a suggestion from @DarkSquirrel42, is to use an InjectionFactory. The downside is that the code still needs updating every time a new constructor parameter is added to something in the chain. The advantages are much easier to understand code, and only a single registration into the container. Func<IUnityContainer,object> createChain = container … Read more
I’m sure there’s a lot of ways code could call SynchronizedLifetimeManager, or a descendant like ContainerControlledLifetimeManager, but there were two scenarios in particular that were causing me problems. The first was my own fault – I was using constructor injection to supply a reference to the container, and in that constructor I was also adding … Read more