unity-container

Say, that I have the following project structure: Application <-> BusinessLogic <-> DataAccessLayer I've prepared all types to use poor-man's-dependency-injection and now I want to introduce the real one using Unity. But I'm struggling on where to put the dependency container and its configuration (i suppose I'll configure it from code). DataAccessLayer needs to register Context (EF) BusinessLogic needs to register data repositories (which use context) Application needs to register services (which use repositories) For now, the only assembly, which uses the container to actually instantiate

I have a class that implements two interfaces, and I want to apply interception to the class's methods. I'm following the advice in Unity Register two interfaces as one singleton , but I'm surprised by the results. In a nutshell, it seems that my CallHandler is called twice. The shortest example I have is this: public interface I1 { void Method1(); } public interface I2 { void Method2(); } public class C : I1, I2 { [Log] public void Method1() {} public void Method2() {} } public class LogAttribute : HandlerAttribute { public override ICallHandler CreateHandler(IUnityContainer container) {

I'm trying to get dependency injection working in an ASP.NET MVC 3 application using Microsoft Unity. First i have implemented my own IDependencyResolver and activated it in my Global.asax file like so: DependencyResolver.SetResolver(new UnityDependencyResolver(container)); I found that i don't need to do anything else to get controller injection (via both the constructor and [Dependency] attribute) to work. With the default view engine i also found i could get the [Dependency] attribute to work in the standard views but not the Layout views. Is it possible to get this to work for the Layout

class Entity:IEntityName { #region IEntityName Members public string FirstName { get; set; } public string LastName { get; set; } #endregion } public class Person:IPerson { public IEntityName EntityName; public Person() { } public Person(IEntityName EntityName) { this.EntityName = EntityName; } public string ReverseName() { return string.Format("Your reverse name is {0} {1}",EntityName.LastName, EntityName.FirstName); } public override string ToString() { return string.Format("Name is {0} {1}", EntityName.FirstName, EntityName.LastName); } } // Main Method private static string

do any other .NET IoC containers provide equivalent functionality to the typed factory facility in Castle Windsor? e.g. if I am using an abstract factory pattern in a WPF application: public class MyViewModel { private IAnotherViewModelFactory factory; public void ShowAnotherViewModel() { viewController.ShowView(factory.GetAnotherViewModel()); } } I don't want to have to create a manual implementation of IAnotherViewModelFactory for every type of ViewModel I wish to show, I want the container to take care of this for me. AutoFac has a feature called Delegate Factories , but as far as I can

Can anyone shed some light on the advantages and disadvantages of using a custom ActionInvoker like so to perform dependency injection on custom ActionFilters as opposed to using a custom FilterProvider as demonstrated here ? In both cases you are going to still want to avoid constructor injection on your ActionFilters, and to me it seems that all the custom FilterProvider does in this case is adds additional overhead of having to register your ActionFilters and the provider in your container. The big advantage of filter providers is that it allows constructor injection if done right. The

I can't get dependency injection working with a custom ActionFilterAttribute class using the Unity bootstrapper for ASP.NET Web API nuget package. I've registered the type in UnityConfig and I'm using it elsewhere (using constructor injection there though) and it works fine. public static void RegisterTypes(IUnityContainer container) { container.RegisterType<ISettingService, SettingService>(); ... } The code is being called successfully, however the instantiated object (settingService) is null. public class APIKeyValidationAttribute : ActionFilterAttribute { [Dependency] public ISettingService

How to do it in code is explained here: Unity Register two interfaces as one singleton _container.RegisterType<EventService>(new ContainerControlledLifetimeManager()); _container.RegisterType<IEventService, EventService>(); _container.RegisterType<IEventServiceInformation, EventService>(); bool singleton = ReferenceEquals(_container.Resolve<IEventService>(), _container.Resolve<IEventServiceInformation>()); How to do it in the XML config? Personally I like to spell out namespaces and assemblies in aliases. So xml: <unity xmlns="http://schemas.microsoft.com/practices/2010/unity"> <alias alias=