You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@satyajit-behera seems this feature request was raised several times and if I correctly remember - there was a comment that such an approach is some kind of anti-pattern and container will not be support this feature (but maybe things will change) https://github.com/dmytrohridin/DependencyInjectionNamedExtensions
I implement for my several projects extensions, it's in prerelease state and testing, but you can try and submit issue if needed
Triage: This isn't something we plan to do in the built-in container. Features we add to the built-in container are likely to be depended-upon by app developers and libraries, which means we have to take extreme care to ensure we support features that most external containers support.
The recommended approach here is to use a container that supports the features your app needed.
While using Microsoft Built In Dependency Injection, need of one feature often comes up:
Passing Parameters to Resolve during runtime.
Autofac provides this as in the example below.
var reader = scope.Resolve<ConfigReader>(new NamedParameter("configSectionName", "sectionName"));
In my opinion, this one feature will make the container complete in many aspects to use for any application that we create.
Is it still available and I am missing it how to use it, Or can it be included in some future release Or is there any work around to implement this?
Thanks
The text was updated successfully, but these errors were encountered: