Dependency injection by type names












0















For my example I use Autofac (it's not necessary):



var r = builder.RegisterType<Helper>().As<IHelper>(); // usual using


What I'd like to do is to be able to register types somehow like:



string name1 = "Helper";



string name2 = "IHelper";



var r = builder.RegisterType<GetTypeFromName(name1)>().As<GetTypeFromName(name2)>();


Is it possible to do with reflection magic?






c# .net reflection dependency-injection autofac







share|improve this question

























  • Possible duplicate of How do I use reflection to call a generic method?

    – thehennyy
    Nov 13 '18 at 19:26
















0















For my example I use Autofac (it's not necessary):



var r = builder.RegisterType<Helper>().As<IHelper>(); // usual using


What I'd like to do is to be able to register types somehow like:



string name1 = "Helper";



string name2 = "IHelper";



var r = builder.RegisterType<GetTypeFromName(name1)>().As<GetTypeFromName(name2)>();


Is it possible to do with reflection magic?






c# .net reflection dependency-injection autofac







share|improve this question

























  • Possible duplicate of How do I use reflection to call a generic method?

    – thehennyy
    Nov 13 '18 at 19:26














0












0








0








For my example I use Autofac (it's not necessary):



var r = builder.RegisterType<Helper>().As<IHelper>(); // usual using


What I'd like to do is to be able to register types somehow like:



string name1 = "Helper";



string name2 = "IHelper";



var r = builder.RegisterType<GetTypeFromName(name1)>().As<GetTypeFromName(name2)>();


Is it possible to do with reflection magic?






c# .net reflection dependency-injection autofac







share|improve this question
















For my example I use Autofac (it's not necessary):



var r = builder.RegisterType<Helper>().As<IHelper>(); // usual using


What I'd like to do is to be able to register types somehow like:



string name1 = "Helper";



string name2 = "IHelper";



var r = builder.RegisterType<GetTypeFromName(name1)>().As<GetTypeFromName(name2)>();


Is it possible to do with reflection magic?






c# .net reflection dependency-injection autofac




c# .net reflection dependency-injection autofac






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 14 '18 at 13:03









Steven

127k17213330




127k17213330










asked Nov 13 '18 at 18:25









amplifieramplifier

490421




490421













  • Possible duplicate of How do I use reflection to call a generic method?

    – thehennyy
    Nov 13 '18 at 19:26



















  • Possible duplicate of How do I use reflection to call a generic method?

    – thehennyy
    Nov 13 '18 at 19:26

















Possible duplicate of How do I use reflection to call a generic method?

– thehennyy
Nov 13 '18 at 19:26





Possible duplicate of How do I use reflection to call a generic method?

– thehennyy
Nov 13 '18 at 19:26












3 Answers
3






active

oldest

votes


















1














You would have to create a mechanism that would "figure out" which concrete types you want to register and how to expose them (the As part in AutoFac). Here is a sample of how you can register using System.Type so the missing part is obtaining the System.Types yourself.



// get your Type(s)

Type concreteType = typeof(Helper);

Type asType = typeof(IHelper);



// Autofac registration call

builder.RegisterType(concreteType).As(asType);


As you can see in the above code you should call the non-generic version of the RegisterType and As methods. (The generic versions really just call down to these anyways).






share|improve this answer


























  • Hey, I even didn't think about non-generic version! Yes, I'm able to get both types, but unfortunately after resolving I get ComponentNotRegisteredException for 'asType' (IHelper). Any ideas?

    – amplifier
    Nov 13 '18 at 18:51











  • @amplifier - Does type Helper implement interface IHelper?

    – Igor
    Nov 13 '18 at 18:53











  • Yes, it does. Checked it, otherwise my "static" resolver wouldn't work

    – amplifier
    Nov 13 '18 at 19:11



















1














Generally to resolve a type name you would need to provide more information than just the class name. So I guess the answer is "not exactly".



The method for mapping a string to a type is Type.GetType, which is documented here: https://docs.microsoft.com/en-us/dotnet/api/system.type.gettype?view=netframework-4.7.2



As you can see, in a vacuum we can't say that "Helper" or "IHelper" would be sufficient. You probably could get by with a namespace-qualified class name. (The reason why Helper works in the "hard-coded" syntax, of course, is that the compiler can take advantage of using statements in deciding what Helper should mean. That option doesn't work when GetType is trying to understand a string at runtime.)



If you can provide a custom resolver, maybe you can make it work exactly as you describe.






share|improve this answer


























  • I can get type variable for Helper and IHelper this way: Type typeArgument = Assembly.LoadFrom(assemblyPath).GetTypes().First(t => t.Name == className);

    – amplifier
    Nov 13 '18 at 18:37













  • Sure, and if that suits your use case, it's fine. This means that you know what assembly the class comes from, which is a good place to start. But also beware of that First method, which may not do what you want if the assembly should happen to contain two classes (in different namespaces) with the same name.

    – Mark Adelsberger
    Nov 13 '18 at 18:41



















1














If you're able to get te Type object for the type you want to register, you can pass it to Autofac using a different overload of the RegisterType method, like so:



var type = Assembly.LoadFrom(path).GetType(typeName);

builder.RegisterType(type);





share|improve this answer
























  • Great! But after resolving IHelper via _container.Resolve<IHelper>(); I get ComponentNotRegisteredException for 'asType' (IHelper).

    – amplifier
    Nov 13 '18 at 18:53











  • If concrete type and interface types are different, you still have to use the As() method as you did before.

    – John Wu
    Nov 13 '18 at 19:04











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53287342%2fdependency-injection-by-type-names%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























3 Answers
3






active

oldest

votes








3 Answers
3






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














You would have to create a mechanism that would "figure out" which concrete types you want to register and how to expose them (the As part in AutoFac). Here is a sample of how you can register using System.Type so the missing part is obtaining the System.Types yourself.



// get your Type(s)

Type concreteType = typeof(Helper);

Type asType = typeof(IHelper);



// Autofac registration call

builder.RegisterType(concreteType).As(asType);


As you can see in the above code you should call the non-generic version of the RegisterType and As methods. (The generic versions really just call down to these anyways).






share|improve this answer


























  • Hey, I even didn't think about non-generic version! Yes, I'm able to get both types, but unfortunately after resolving I get ComponentNotRegisteredException for 'asType' (IHelper). Any ideas?

    – amplifier
    Nov 13 '18 at 18:51











  • @amplifier - Does type Helper implement interface IHelper?

    – Igor
    Nov 13 '18 at 18:53











  • Yes, it does. Checked it, otherwise my "static" resolver wouldn't work

    – amplifier
    Nov 13 '18 at 19:11
















1














You would have to create a mechanism that would "figure out" which concrete types you want to register and how to expose them (the As part in AutoFac). Here is a sample of how you can register using System.Type so the missing part is obtaining the System.Types yourself.



// get your Type(s)

Type concreteType = typeof(Helper);

Type asType = typeof(IHelper);



// Autofac registration call

builder.RegisterType(concreteType).As(asType);


As you can see in the above code you should call the non-generic version of the RegisterType and As methods. (The generic versions really just call down to these anyways).






share|improve this answer


























  • Hey, I even didn't think about non-generic version! Yes, I'm able to get both types, but unfortunately after resolving I get ComponentNotRegisteredException for 'asType' (IHelper). Any ideas?

    – amplifier
    Nov 13 '18 at 18:51











  • @amplifier - Does type Helper implement interface IHelper?

    – Igor
    Nov 13 '18 at 18:53











  • Yes, it does. Checked it, otherwise my "static" resolver wouldn't work

    – amplifier
    Nov 13 '18 at 19:11














1












1








1







You would have to create a mechanism that would "figure out" which concrete types you want to register and how to expose them (the As part in AutoFac). Here is a sample of how you can register using System.Type so the missing part is obtaining the System.Types yourself.



// get your Type(s)

Type concreteType = typeof(Helper);

Type asType = typeof(IHelper);



// Autofac registration call

builder.RegisterType(concreteType).As(asType);


As you can see in the above code you should call the non-generic version of the RegisterType and As methods. (The generic versions really just call down to these anyways).






share|improve this answer















You would have to create a mechanism that would "figure out" which concrete types you want to register and how to expose them (the As part in AutoFac). Here is a sample of how you can register using System.Type so the missing part is obtaining the System.Types yourself.



// get your Type(s)

Type concreteType = typeof(Helper);

Type asType = typeof(IHelper);



// Autofac registration call

builder.RegisterType(concreteType).As(asType);


As you can see in the above code you should call the non-generic version of the RegisterType and As methods. (The generic versions really just call down to these anyways).







share|improve this answer














share|improve this answer



share|improve this answer








edited Nov 13 '18 at 18:43

























answered Nov 13 '18 at 18:32









IgorIgor

39.4k349102




39.4k349102













  • Hey, I even didn't think about non-generic version! Yes, I'm able to get both types, but unfortunately after resolving I get ComponentNotRegisteredException for 'asType' (IHelper). Any ideas?

    – amplifier
    Nov 13 '18 at 18:51











  • @amplifier - Does type Helper implement interface IHelper?

    – Igor
    Nov 13 '18 at 18:53











  • Yes, it does. Checked it, otherwise my "static" resolver wouldn't work

    – amplifier
    Nov 13 '18 at 19:11



















  • Hey, I even didn't think about non-generic version! Yes, I'm able to get both types, but unfortunately after resolving I get ComponentNotRegisteredException for 'asType' (IHelper). Any ideas?

    – amplifier
    Nov 13 '18 at 18:51











  • @amplifier - Does type Helper implement interface IHelper?

    – Igor
    Nov 13 '18 at 18:53











  • Yes, it does. Checked it, otherwise my "static" resolver wouldn't work

    – amplifier
    Nov 13 '18 at 19:11

















Hey, I even didn't think about non-generic version! Yes, I'm able to get both types, but unfortunately after resolving I get ComponentNotRegisteredException for 'asType' (IHelper). Any ideas?

– amplifier
Nov 13 '18 at 18:51





Hey, I even didn't think about non-generic version! Yes, I'm able to get both types, but unfortunately after resolving I get ComponentNotRegisteredException for 'asType' (IHelper). Any ideas?

– amplifier
Nov 13 '18 at 18:51













@amplifier - Does type Helper implement interface IHelper?

– Igor
Nov 13 '18 at 18:53





@amplifier - Does type Helper implement interface IHelper?

– Igor
Nov 13 '18 at 18:53













Yes, it does. Checked it, otherwise my "static" resolver wouldn't work

– amplifier
Nov 13 '18 at 19:11





Yes, it does. Checked it, otherwise my "static" resolver wouldn't work

– amplifier
Nov 13 '18 at 19:11













1














Generally to resolve a type name you would need to provide more information than just the class name. So I guess the answer is "not exactly".



The method for mapping a string to a type is Type.GetType, which is documented here: https://docs.microsoft.com/en-us/dotnet/api/system.type.gettype?view=netframework-4.7.2



As you can see, in a vacuum we can't say that "Helper" or "IHelper" would be sufficient. You probably could get by with a namespace-qualified class name. (The reason why Helper works in the "hard-coded" syntax, of course, is that the compiler can take advantage of using statements in deciding what Helper should mean. That option doesn't work when GetType is trying to understand a string at runtime.)



If you can provide a custom resolver, maybe you can make it work exactly as you describe.






share|improve this answer


























  • I can get type variable for Helper and IHelper this way: Type typeArgument = Assembly.LoadFrom(assemblyPath).GetTypes().First(t => t.Name == className);

    – amplifier
    Nov 13 '18 at 18:37













  • Sure, and if that suits your use case, it's fine. This means that you know what assembly the class comes from, which is a good place to start. But also beware of that First method, which may not do what you want if the assembly should happen to contain two classes (in different namespaces) with the same name.

    – Mark Adelsberger
    Nov 13 '18 at 18:41
















1














Generally to resolve a type name you would need to provide more information than just the class name. So I guess the answer is "not exactly".



The method for mapping a string to a type is Type.GetType, which is documented here: https://docs.microsoft.com/en-us/dotnet/api/system.type.gettype?view=netframework-4.7.2



As you can see, in a vacuum we can't say that "Helper" or "IHelper" would be sufficient. You probably could get by with a namespace-qualified class name. (The reason why Helper works in the "hard-coded" syntax, of course, is that the compiler can take advantage of using statements in deciding what Helper should mean. That option doesn't work when GetType is trying to understand a string at runtime.)



If you can provide a custom resolver, maybe you can make it work exactly as you describe.






share|improve this answer


























  • I can get type variable for Helper and IHelper this way: Type typeArgument = Assembly.LoadFrom(assemblyPath).GetTypes().First(t => t.Name == className);

    – amplifier
    Nov 13 '18 at 18:37













  • Sure, and if that suits your use case, it's fine. This means that you know what assembly the class comes from, which is a good place to start. But also beware of that First method, which may not do what you want if the assembly should happen to contain two classes (in different namespaces) with the same name.

    – Mark Adelsberger
    Nov 13 '18 at 18:41














1












1








1







Generally to resolve a type name you would need to provide more information than just the class name. So I guess the answer is "not exactly".



The method for mapping a string to a type is Type.GetType, which is documented here: https://docs.microsoft.com/en-us/dotnet/api/system.type.gettype?view=netframework-4.7.2



As you can see, in a vacuum we can't say that "Helper" or "IHelper" would be sufficient. You probably could get by with a namespace-qualified class name. (The reason why Helper works in the "hard-coded" syntax, of course, is that the compiler can take advantage of using statements in deciding what Helper should mean. That option doesn't work when GetType is trying to understand a string at runtime.)



If you can provide a custom resolver, maybe you can make it work exactly as you describe.






share|improve this answer















Generally to resolve a type name you would need to provide more information than just the class name. So I guess the answer is "not exactly".



The method for mapping a string to a type is Type.GetType, which is documented here: https://docs.microsoft.com/en-us/dotnet/api/system.type.gettype?view=netframework-4.7.2



As you can see, in a vacuum we can't say that "Helper" or "IHelper" would be sufficient. You probably could get by with a namespace-qualified class name. (The reason why Helper works in the "hard-coded" syntax, of course, is that the compiler can take advantage of using statements in deciding what Helper should mean. That option doesn't work when GetType is trying to understand a string at runtime.)



If you can provide a custom resolver, maybe you can make it work exactly as you describe.







share|improve this answer














share|improve this answer



share|improve this answer








edited Nov 13 '18 at 18:38

























answered Nov 13 '18 at 18:33









Mark AdelsbergerMark Adelsberger

20.2k11221




20.2k11221













  • I can get type variable for Helper and IHelper this way: Type typeArgument = Assembly.LoadFrom(assemblyPath).GetTypes().First(t => t.Name == className);

    – amplifier
    Nov 13 '18 at 18:37













  • Sure, and if that suits your use case, it's fine. This means that you know what assembly the class comes from, which is a good place to start. But also beware of that First method, which may not do what you want if the assembly should happen to contain two classes (in different namespaces) with the same name.

    – Mark Adelsberger
    Nov 13 '18 at 18:41



















  • I can get type variable for Helper and IHelper this way: Type typeArgument = Assembly.LoadFrom(assemblyPath).GetTypes().First(t => t.Name == className);

    – amplifier
    Nov 13 '18 at 18:37













  • Sure, and if that suits your use case, it's fine. This means that you know what assembly the class comes from, which is a good place to start. But also beware of that First method, which may not do what you want if the assembly should happen to contain two classes (in different namespaces) with the same name.

    – Mark Adelsberger
    Nov 13 '18 at 18:41

















I can get type variable for Helper and IHelper this way: Type typeArgument = Assembly.LoadFrom(assemblyPath).GetTypes().First(t => t.Name == className);

– amplifier
Nov 13 '18 at 18:37







I can get type variable for Helper and IHelper this way: Type typeArgument = Assembly.LoadFrom(assemblyPath).GetTypes().First(t => t.Name == className);

– amplifier
Nov 13 '18 at 18:37















Sure, and if that suits your use case, it's fine. This means that you know what assembly the class comes from, which is a good place to start. But also beware of that First method, which may not do what you want if the assembly should happen to contain two classes (in different namespaces) with the same name.

– Mark Adelsberger
Nov 13 '18 at 18:41





Sure, and if that suits your use case, it's fine. This means that you know what assembly the class comes from, which is a good place to start. But also beware of that First method, which may not do what you want if the assembly should happen to contain two classes (in different namespaces) with the same name.

– Mark Adelsberger
Nov 13 '18 at 18:41











1














If you're able to get te Type object for the type you want to register, you can pass it to Autofac using a different overload of the RegisterType method, like so:



var type = Assembly.LoadFrom(path).GetType(typeName);

builder.RegisterType(type);





share|improve this answer
























  • Great! But after resolving IHelper via _container.Resolve<IHelper>(); I get ComponentNotRegisteredException for 'asType' (IHelper).

    – amplifier
    Nov 13 '18 at 18:53











  • If concrete type and interface types are different, you still have to use the As() method as you did before.

    – John Wu
    Nov 13 '18 at 19:04
















1














If you're able to get te Type object for the type you want to register, you can pass it to Autofac using a different overload of the RegisterType method, like so:



var type = Assembly.LoadFrom(path).GetType(typeName);

builder.RegisterType(type);





share|improve this answer
























  • Great! But after resolving IHelper via _container.Resolve<IHelper>(); I get ComponentNotRegisteredException for 'asType' (IHelper).

    – amplifier
    Nov 13 '18 at 18:53











  • If concrete type and interface types are different, you still have to use the As() method as you did before.

    – John Wu
    Nov 13 '18 at 19:04














1












1








1







If you're able to get te Type object for the type you want to register, you can pass it to Autofac using a different overload of the RegisterType method, like so:



var type = Assembly.LoadFrom(path).GetType(typeName);

builder.RegisterType(type);





share|improve this answer













If you're able to get te Type object for the type you want to register, you can pass it to Autofac using a different overload of the RegisterType method, like so:



var type = Assembly.LoadFrom(path).GetType(typeName);

builder.RegisterType(type);






share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 13 '18 at 18:46









John WuJohn Wu

29.9k42752




29.9k42752













  • Great! But after resolving IHelper via _container.Resolve<IHelper>(); I get ComponentNotRegisteredException for 'asType' (IHelper).

    – amplifier
    Nov 13 '18 at 18:53











  • If concrete type and interface types are different, you still have to use the As() method as you did before.

    – John Wu
    Nov 13 '18 at 19:04



















  • Great! But after resolving IHelper via _container.Resolve<IHelper>(); I get ComponentNotRegisteredException for 'asType' (IHelper).

    – amplifier
    Nov 13 '18 at 18:53











  • If concrete type and interface types are different, you still have to use the As() method as you did before.

    – John Wu
    Nov 13 '18 at 19:04

















Great! But after resolving IHelper via _container.Resolve<IHelper>(); I get ComponentNotRegisteredException for 'asType' (IHelper).

– amplifier
Nov 13 '18 at 18:53





Great! But after resolving IHelper via _container.Resolve<IHelper>(); I get ComponentNotRegisteredException for 'asType' (IHelper).

– amplifier
Nov 13 '18 at 18:53













If concrete type and interface types are different, you still have to use the As() method as you did before.

– John Wu
Nov 13 '18 at 19:04





If concrete type and interface types are different, you still have to use the As() method as you did before.

– John Wu
Nov 13 '18 at 19:04


















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53287342%2fdependency-injection-by-type-names%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

Xamarin.iOS Cant Deploy on Iphone

Image
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } -1 I have a windows laptop and a mac mini my problem is that It wont deploy on iphone if I use Visual Studio Xamarin on windows to install my app, but it works fine with Visual Studio For Mac. Here's what I get after build succeded on Visual Studio Xamarin on windows : 1>------ Build started: Project: FinalCustomerApp.iOS, Configuration: Debug iPhone ------ 1> Connecting to Mac server 192.168.8.100... 1> FinalCustomerApp.iOS -> C:UsersJeremy PaulDesktopFinalCustomerAppFinalCustomerAppFinalCustomerApp.iOSbiniPhoneDebugFinalCustomerApp.iOS.exe 1> Detected signing identity: 1> Code Signing Key: &quo
Read more

Glorious Revolution

Image
"The Bloodless Revolution" redirects here. For a history of the vegetarian movement, see The Bloodless Revolution (book). This article is about the English revolution of 1688. For the revolution of 1868 in Spain, see Glorious Revolution (Spain). For other uses, see Glorious Revolution (disambiguation). Glorious Revolution The Prince of Orange lands at Torbay Date 1688–1689 Location British Isles Also known as Revolution of 1688 War of the English Succession Bloodless Revolution Participants English, Welsh and Scottish society, Dutch forces Outcome Replacement of James II by William III and Mary II Jacobite rising of 1689 Williamite War in Ireland War with France; England and Scotland join Grand Alliance Drafting of the Bill of Rights 1689 Part of a series on the History of England Timeline Prehistoric Britain Roman Britain Sub-Roman Britain Medieval period Economy in the Middle Ages Anglo-Saxon period
Read more

Dulmage-Mendelsohn matrix decomposition in Python

Image
0 Matlab has a function called dmperm that computes the so-called Dulmage–Mendelsohn decomposition of a n x n matrix. From wikipedia, the Dulmage–Mendelsohn is a partition of the vertices of a bipartite graph into subsets, with the property that two adjacent vertices belong to the same subset if and only if they are paired with each other in a perfect matching of the graph. Looking both on scipy and numpy, I could not find this function, nor some similar version. Is it possible to implement it using basic linear algebra operations? Any idea if this is implemented in some Python package? python matlab linear-algebra graph-theory matrix-decomposition share | improve this question
Read more