No default instance or named instance 'Default' for requested plugin type

早过忘川 提交于 2019-12-13 05:19:45

问题


I'm trying to avoid referencing the concrete type library in my main project, but I'm getting this error:

No default instance or named instance 'Default' for requested plugin type StackExchangeChatInterfaces.IClient
1.) Container.GetInstance(StackExchangeChatInterfaces.IClient ,{username=; password=; defaultRoomUrl=; System.Action`2[System.Object,System.Object]=System.Action`2[System.Object,System.Object]})

I've setup my container to scan for assemblies, like so:

        var container = new Container(x =>
        {
            x.Scan(scan =>
            {
                scan.AssembliesFromApplicationBaseDirectory();
                scan.ExcludeNamespace("StructureMap");
                scan.WithDefaultConventions();
                scan.AddAllTypesOf<IMessageHandlers>();
            });
            //x.For<IClient>().Use<Client>(); //GetInstance will work if this line is not commented out.
        });

When I try to get an instance, I get the error, my code for getting an instance is here:

chatInterface = container
    .With("username").EqualTo(username)
    .With("password").EqualTo(password)
    .With("defaultRoomUrl").EqualTo(roomUrl)
    .With<Action<object, object>>(delegate(object sender, object messageWrapper)
        {
            string message = ((dynamic)messageWrapper).Message;
            Console.WriteLine("");
            Console.WriteLine(message);
            foreach (var item in messageHandlers)
            {
                item.MessageHandler.Invoke(message, chatInterface);
            }                        
        }).GetInstance<IClient>();

If I explicitly map the concrete class to the interface, everything works hunky dory, but that means I need to reference the project that Client is in, which I don't want to do.


回答1:


This is really interesting. Looks like default conventions are not able to register types with such constructor (tried on both versions 2.6.3 and 3+). I was only registered when only parameterless constructor was specified. Looking at sources of both versions it is really suspicious as it should be registered. Deeper dive into the code would be needed...

Anyway try using custom registration convention:

public class ClientConvention : IRegistrationConvention
{
    public void Process(Type type, Registry registry)
    {
        if (type.IsClass && !type.IsAbstract && !type.IsGenericType &&
            type.GetInterfaces().Contains(typeof(IClient)))
        {
            registry.For(typeof(IClient)).Use(type);
        }
    }
}

Configure it like this:

    var container = new Container(
            c => c.Scan(
                s =>
                    {
                         s.ExcludeNamespace("StructureMap");
                         s.WithDefaultConventions();
                         s.Convention<ClientConvention>();
                         s.AddAllTypesOf<IMessageHandlers>();
                    }));

and this should work just fine.




回答2:


The default type scanning will not pick up concrete types whose constructor functions contain primitive arguments like strings, numbers, or dates. The thinking is that you'd effectively have to explicitly configure those inline dependencies anyway.

"but that means I need to reference the project that Client is in, which I don't want to do."

  • Does that actually matter? I think you're making things harder than they have to be by trying to eliminate the assembly reference.


来源:https://stackoverflow.com/questions/27362433/no-default-instance-or-named-instance-default-for-requested-plugin-type

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!