unity-container

问题 I am new with the dependency injection pattern. I'm a little confused about few things. Scenario: I have a class library project called 'MailCore'. This project has interfaces and classes that perform all email sending stuff. I have an MVC project called 'The site'. It uses the 'MailCore' project to send email. I have Unity in this project and the UnityContainer is registered and things are working fine. I also have another class library library project called 'SiteRepo'. Sometimes, to

问题 we want to use Unity for IOC. All i've seen is the implementation that there is one global static service (let's call it the the IOCService) which holds a reference to the Unity container, which registers all interface/class combinations and every class asks that object: give me an implementation for Ithis or IThat. Frequently i see a response that this pattern is not good because it leads to a dependency from ALL classes to the IOCService (not to the Unity container because it is only known

问题 We have Unity+Prism WPF applications, and there is 2 folders from which we want to load dynamically the modules. I know that to load modules from a directory, I should use a DirectoryModuleCatalog , but the CreateModuleCatalog method allows only one catalog to be returned, so how do I wrap them in one catalog? In my boostrapper, what should I return here: protected override IModuleCatalog CreateModuleCatalog() { new DirectoryModuleCatalog() { ModulePath = @".\Services" }; new

问题 We have Unity+Prism WPF applications, and there is 2 folders from which we want to load dynamically the modules. I know that to load modules from a directory, I should use a DirectoryModuleCatalog , but the CreateModuleCatalog method allows only one catalog to be returned, so how do I wrap them in one catalog? In my boostrapper, what should I return here: protected override IModuleCatalog CreateModuleCatalog() { new DirectoryModuleCatalog() { ModulePath = @".\Services" }; new

问题 I'm trying to use the Unity Registration by Convention feature. I can't figure out how to register from specific assembly/project files with the file ending "Repository". container.RegisterTypes( AllClasses.FromAssembliesInBasePath(), WithMappings.FromMatchingInterface, WithName.Default, WithLifetime.ContainerControlled); I've found only this example from a MSDN blog ( https://blogs.msdn.microsoft.com/agile/2013/03/12/unity-configuration-registration-by-convention/ ) post and as I understand

问题 What I want: Resolve object A, and inside object A, I want use same container to resolve object C: public static void Work() { IUnityContainer con = new UnityContainer(); con.RegisterType<IA, A>(); con.RegisterType<IB, B>(); con.RegisterType<IC, C>(); var a = con.Resolve<IA>(); } interface IA { } interface IB { } interface IC { } class A : IA { public A(IB b, IUnityContainer con) { for (int i = 0; i < 10; i++) { var c = con.Resolve<IC>(); } } } class B : IB { }; class C : IC { }; Problem: On

问题 I created an Microsoft unity project (my first using Dependency Injection) with my home controller working fine as expected having registered my messaging Class as follows private static IUnityContainer BuildUnityContainer() { var container = new UnityContainer(); container.RegisterType<IMessageService, MessageService>(new HierarchicalLifetimeManager()); RegisterTypes(container); return container; } The challenge is I intend making this project a parent to several modules that will be plugins

问题 I am facing problem with disposing unnecessary objects from DI container. I use Prism for Xamarin.Forms with Unity container. Application gets configuration from some database, creates some services using this configuration and registers this services in container using ContainerControlledLifetimeManager. This services are used while resolving views and viewmodels. When configuration changes application retrieves again changed configuration and now problem comes: how can I remove previous

问题 I would like to update from 6.3 to 7. I seem to have hit a road block. When using the PrismApplication class in the App.xaml, CreateShell expects a return type of Window instead of the previous BootStrapper which wanted a DependencyObject. My MainShell is a modified Telerik RadWindow which itself is a modified System.Windows.Controls.HeaderedContentControl and casting to Window is not possible. Is there a way around this so I can use the PrismApplication object or do I have to roll back and

问题 On trying to resolve my service class, I'm getting an error that DbContext cannot be constructed because it's an abstract class. The error message is here: Unity.Exceptions.ResolutionFailedException: 'Resolution of the dependency failed, type = 'MyService.MyClass', name = '(none)'. Exception occurred while: while resolving. Exception is: InvalidOperationException - The current type, System.Data.Common.DbConnection, is an abstract class and cannot be constructed. Are you missing a type mapping