autofac

问题 Given the example dependency tree below I would like to select the bottom level Config instance based on the top level dependency being resolved from the container e.g. TopLevelMessageConsumer would resolve the same IMessageService & IMessageQueue implementations as TopLevelMessageDispatcher but each would have their own Config instance. - TopLevelMessageConsumer - IMessageService - IMessageQueue - Config - TopLevelMessageDispatcher - IMessageService - IMessageQueue - Config I know this is

问题 I am attempting to intercept methods on a WCF service server side with the following registration: containerBuilder.RegisterType<Service>().As<IServiceContract>().InstancePerLifetimeScope() .EnableInterfaceInterceptors().InterceptedBy(typeof(MethodInterceptor)); however, when I do the service endpoint disappears. The WCF service is hosted inside a Windows Service. Any ideas? The exception I receive is as follows: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening

问题 I have an ASP.NET web application which until now has been using an Autofac configuration class which has specified an InstancePerRequest() for services in the application. Since then, I have created a new console application in the same solution which will be responsible for running automated job processes. Since I can't use the InstancePerRequest configuration for my console application, then I need to make a change to my configuration. Ideally, I don't want to copy and paste all the

问题 I've got an application where a shared object needs a reference to a per-request object. Shared: Engine | Per Req: IExtensions() | Request If i try to inject the IExtensions directly into the constructor of Engine , even as Lazy(Of IExtension) , I get a "No scope matching [Request] is visible from the scope in which the instance was requested." exception when it tries to instantiate each IExtension . How can I create a HttpRequestScoped instance and then inject it into a shared instance?

问题 When using Autofac with ASP.NET Web API, is there any way to resolve dependencies using the services registered in HttpConfiguration or even the HttpConfiguration itself. For instance, I would like to have a controller with a constructor that receives the config's registered ITraceWriter or the HttpConfiguration itself. I know that the configuration is available in the action methods, but I would like to use it in the constructor. Thanks. edit 1 I've found a way to make the current

问题 I'm using NLog with this module: public class LoggingModule : Autofac.Module { protected override void AttachToComponentRegistration(IComponentRegistry componentRegistry, IComponentRegistration registration) { registration.Preparing += OnComponentPreparing; registration.Activated += (sender, e) => InjectLoggerProperties(e.Instance); } private static void OnComponentPreparing(object sender, PreparingEventArgs e) { var t = e.Component.Activator.LimitType; e.Parameters = e.Parameters.Union( new[

问题 I'm using entity framework 6 and Autofac in my web application. I inject unit of work with DbContext inside, both externally owned so I can dispose them myself. DbContext registered PerLifetimeScope, Unit of work is a factory, therefore registered as per dependency. When Executing the first http Get action everthing works fine and I see the unit of work with the context are disposed after the response is coming from the db which is great. My issue is that whenever I execute a second request,

问题 I have a generic UnitOfWork pattern implementation and these UnitOfWork objects are dependencies to my service classes. Below snippets should help the reader understand my code setup: IUnitOfWork interface public interface IUnitOfWork<out TContext> where TContext : IDbContext UnitOfWork class public sealed class UnitOfWork<TContext> : IDisposable, IUnitOfWork<IDbContext> where TContext : IDbContext { private static readonly ILog Log = LogManager.GetLogger(typeof(UnitOfWork<TContext>));

问题 I'm having hard time integrating autofac in my applcation.. My application integrates with other applications, when a connection to another application is made its being maintained by a fitting "Protocol" object // This class is inherited by a few other classes public abstract class Protocol I have a layer that is run by it's own thread and handles connection requests. For each kind of request a different kind of protocol is created (a different protocol object) // For example lets say every

问题 Why and when should we use PreserveExistingDefaults during autofac registration? I have read it's uses form Autoface docs: http://docs.autofac.org/en/latest/register/registration.html But my question is, when is the case we will register multiple implementation with single interface. Can anybody give some example from real time. 回答1: It can be use when you want to register a new implementation without changing the default one. When you register multiple registration for a single interface,