unity-container

I've set up Unity for dependency injection for our project. The project itself is an ASP.NET application that uses both MVC and Web API. For the database context, I'm using the PerRequestLifetimeManager . This is done so that the different bits of business logic are using the same context (and thus the same transaction). In order to be able to use the PerRequestLifetimeManager , I've added references to the nuget packages Unity bootstrapper for ASP.NET MVC and Unity bootstrapper for ASP.NET Web API . For use of this lifetime manager in Web API, the following line has been added to the startup

I have a unity container that I am registering types within like so: IUnityContainer container = new UnityContainer() .RegisterType<ITaxAuthorityRateService, TaxAuthorityPopulationRateService>( "PopulationRate" ) .RegisterType<ITaxAuthorityRateService, TaxAuthorityBusinessLicenseRateService>( "BusinessLicenseRate" ); Then I also want to register 2 different services that take a ITaxAuthorityRateService variable in their constructor. Both services need a different class that derives from ITaxAuthorityRateService. How can I handle that situation? Ok I figured it out. Keeping the names the same

I am trying to implement DI in a webforms project, so I installed the Unity.WebForms dlls in my UI layer. As soon as I did an App_Start folder was created for me with a UnityWebFormsStart class file. Inside this file there is a method RegisterDependencies which asks to be edited. What is the next step after registering the dependencies? Is there something I need to add in the Global.asax class file? And how and where do I resolve a type inside a webform? Do I decorate that with any attributes? The Unity.WebForms dll and NuGet package does a few things for you in the background. It will ensure

I've bumped through a few of these questions laying around various sites and the answers seem to be spun by l4n officianados toward the value of the lightweight wrapper that log4net 'is' (don't you get it?) and similar points of mind-boggling fact. However it seems that what users are asking for (and this is my question) is how to fit the log4net objet model into the registertype/registerinstance sequence in the fluent config interface. The goal here wouldn't be to re-wrap l4n, but simply to grab a decent reference that doesnt' require hijacking the fluent flow, as it were. poor ejemplow, I

I'm using PRISM 4 Navigation API with Unity in WPF. I have a tree-view that initiates a RequestNavigate passing in the selected tree node's ID ( GUID ). _regionManager.RequestNavigate(RegionNames.DetailRegion, ViewNames.SiteView + "?ID=" + site.ID); In my module, I have registered the view/view-model like so: _container.RegisterType<SiteDetailsViewModel>(); _container.RegisterType<object, SiteDetailsView>(ViewNames.SiteView); When I select different nodes from the tree view, the DetailsRegion displays the SiteDetailsView as expected, but when I like to navigate back to the same node, a new

I'm studying up on the unity containers and have a quick question on how to resolve a class's construction to multiple different implementations of an interface. Here's my code: public interface IRenderer { void DrawSquare(Square square); void DrawCircle(Circle circle); } public interface IShape { void Draw(IRenderer renderer); } public class Dx11Renderer : IRenderer { public void DrawSquare(Square square) { } public void DrawCircle(Circle circle) { } } public class GlRenderer : IRenderer { public void DrawSquare(Square square) { } public void DrawCircle(Circle circle) { } } public class

I am working on a middle sized WPF application (MVVM) that should be extensible and maintainable in the future. Thus I decided to use an IoC container (Unity in this case) to keep things flexible. However I am not sure where to place and configure Unity in a WPF application. I guess container should be accessible globally so it should probably go to Application class. But should I make it as static property? Should I configure it in Application_Startup() event handler? Eg: /// <summary> /// Interaction logic for App.xaml /// </summary> public partial class App : Application { public static