New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Autofac integration issue - Ambiguous invocation #7627
Milestone
Comments
I can't reproduce this problem. |
Just add package Volo.Abp.Autofac 4.2.0, in your module, add codes: public override void ConfigureServices(ServiceConfigurationContext context)
{
context.Services.AddAutofac(builder =>
{
});
} the AddAutofac will display ambiguous problem. |
I download a new abp project from https://abp.io/get-started.
public override void ConfigureServices(ServiceConfigurationContext context)
{
context.Services.AddAutofac(builder =>
{
});
}
|
You can temporarily resolve it via: services.AddSingleton<IServiceProviderFactory<ContainerBuilder>>(new AutofacServiceProviderFactory(builder =>
{
})); |
maliming
added a commit
that referenced
this issue
Feb 7, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I upgrade Abp version to 4.2.0, the AddAutofac extension method display CS0121 error: ambiguous between the "AddAutofac" in the Volo.Abp.Autofac and Autofac.Extensions.DependencyInjection 6.0.0.0
And I also create a brand new project in Abp version 4.2.0, and this problem is still exists.
This issue seems cause by PR #6463 which Add Autofac.Extensions.DependencyInjection package to the Volo.Abp.Autofac module
The text was updated successfully, but these errors were encountered: