unity-container

问题 I am using Entity Framework 5 Code First, I use the repository and unit of work pattern, and have my domain models, repositories, and service layer working fine within an MVC app running in a Windows Azure cloud service. I'm using Unity for IoC and inject repositories, controllers, and service classes as required, and use a per-request lifetime. It has been working great. However, when I use the same code/class libraries for the domain, repository, and the EF5 DbContext, in an Azure Worker

问题 So, there's a bug in some legacy code I'm maintaining. It causes some mild data corruption, so it's rather serious. I've found the root cause, and have made a sample application that reliable reproduces the bug. I would like to fix it with as little impact on existing applications as possible, but I'm struggling. The bug lies in the data access layer. More specifically, in how an interceptor is injected into a new Nhibernate Session. The interceptor is used to set a specific entity property

问题 I'm putting the unity container creation/setup in the global.asax. and making the container a static property on that class since i'm not sure how unity works or if the container needs to be kept alive and references elsewhere. What's the recommended location of unity initialization/configuration for mvc 2? 回答1: You shouldn't need to keep an explicit reference around for the container. A container should wire up the requested object graph (Controllers in this case) and get out of the way.

问题 When using this object model: interface IInterface {} class Impl : IInterface { public Impl(int blah) {} } And this test: void Test1() { IUnityContainer container = new UnityContainer(); container.RegisterInstance(new Impl(3), new ContainerControlledLifetimeManager()); container.RegisterType<IInterface, Impl>(new ContainerControlledLifetimeManager()); Impl impl = container.Resolve<Impl>(); } I get an exception: Resolution of the dependency failed, type = "BlahMain.Program+Impl", name = "(none

问题 It appears this is the case. If I am marking a generic as a closed type, I am stating my intention to use a Type and not an Instance of a Type. I am getting an error as Unity is trying to resolve the closing type in the ExternalLinkingRepository class below. The error states that Unity can not reconcile the constructor as there is more than 1 with the same number of parameters (2). I have looked at constructor injectors (and indeed need one for the connection string, but this is not the issue

问题 I have a facade in a library that exposes some complex functionality through a simple interface. My question is how do I do dependency injection for the internal types used in the facade. Let's say my C# library code looks like - public class XYZfacade:IFacade { [Dependency] internal IType1 type1 { get; set; } [Dependency] internal IType2 type2 { get; set; } public string SomeFunction() { return type1.someString(); } } internal class TypeA { .... } internal class TypeB { .... } And my website

问题 We have a standard application in our company. Now I want to inject some custom assemblies in the application. Normally if you have a ninject kernel or unity container, you can get the implementation like below: IKernel kernel = new StandardKernel(); DealerService myServ = new DealerService(kernel.Get<IDealerController>()); DealerService: public partial class DealerService : ServiceBase { private readonly IDealerController Controller; public DealerService(IDealerController controller) {

问题 I have a project containing a xaml ResourceDictionary that I wish to use outside of a FrameworkElement. The resource dictionary will contain a DataTemplate for a class local to the project to avoid polluting the app.xaml (as the project is a prism module, and will not always be present depending on config). So, I have a test.xaml file with a Resource build action. This is intended to supply the DataTemplate for a TestObject class. In the TestObject class I have a GetTemplate() method The

问题 I'm a relative noob to the concept of Dependency Injection, and have been trying to glean the best practices before starting a new project. Looking at the top answer to Dependency injection in unit of work pattern using repositories I understand the approach, but the example code seems to be missing something, and I'm stumped... The definition of the interface IRepository is shown as: public interface IRepository { void Submit(); } But when the interface is used as part of the definition of

问题 I am in this situation where my service interface is being implemented by two service classes. For example, IFooService is implemented by FooService and FooWithExtraInfoService Here is the interface: public interface IFooService { Foo GetEntity(string fieldName, stringFieldValue); } Here is FooService : public class FooService: BarService, IFooService { public FooService(ILogService logservice): base(logservice) { } public Foo GetEntity(string fieldName, string fieldValue) { //here goes the