Ambiguous method call between multiple Moq.AutoMock.AutoMockerKeyedServicesExtensions.WithKeyedService

[burger100]

After upgrading to Moq.AutoMocker 3.6.1, I got the following error in the AutoMocker generated code:

The call is ambiguous between the following methods or properties: 
'Moq.AutoMock.AutoMockerKeyedServicesExtensions.WithKeyedService<TService, TImplementation>(Moq.AutoMock.AutoMocker, TImplementation, object?)' 
and 
'Moq.AutoMock.AutoMockerKeyedServicesExtensions.WithKeyedService<TService, TImplementation>(Moq.AutoMock.AutoMocker, TImplementation, object?)'
In File AutoMockerKeyedServicesExtensions.g.cs

In the source code, I found a test related to this feature flag that validate if the method should be created or not:
EnableMoqAutoMockerKeyedServicesGenerator

Trying to disable it by adding the following to my csproj doesn't work

<PropertyGroup>
 <EnableMoqAutoMockerKeyedServicesGenerator>false</EnableMoqAutoMockerKeyedServicesGenerator>
</PropertyGroup>

[Keboo]

The disabling of the source generator should already be fixed the latest preview package 3.6.2-ci0768. As a quick fix you can update to that, then the flag should properly disable it.

I am surprised to see the ambiguous as the generator is generating an internal type. Can you provide any details on your project structure, including which are referencing the Moq.AutoMock NuGet package, as well as which projects are referencing Microsoft.Extensions.DependencyInjection.Abstractions NuGet package?

[burger100]

Thanks, the preview version with the feature flag fixed the issue like you suggested.

It's a AspNet Core Server on .NET10. Created some years ago so it use the old Program/Startup structure.

/src/Project
  - Program.cs : Host.CreateDefaultBuilder
/src/Project.Bussiness
/src/Project.Storage
/src/Project.Telemetry
/tests/Project.UnitTests
/tests/Project.IntegrationTests
  - CustomWebApplicationFactory: derive from WebApplicationFactory<Startup>

AutoMocker is used only in UnitTest and IntegrationTests of course.

[Keboo]

Is there are project references between your IntegrationTests and UnitTests projects? Any chance there is an InternalsVisibleTo being used in any of these projects?

[laura-lucciola-exclaimer]

We are also seeing this error that I believe it can be related
We are using version 3.6.1

'TClass' must be a non-abstract type with a public parameterless constructor in order to use it as parameter 'TOptions' in the generic type or method 'IOptionsFactory<TOptions>'

We tried both using the preview package 3.6.2-ci0768 and using

<PropertyGroup>
 <EnableMoqAutoMockerKeyedServicesGenerator>false</EnableMoqAutoMockerKeyedServicesGenerator>
</PropertyGroup>

It happens in unit test projects using

    [SetUp]
    public void Setup()
    {
        _mocker = new AutoMocker();
        _mocker.Use<IOptions<MyOptions>>(new OptionsWrapper<MyOptions>(new MyOptions
        {
            Email= "noreply@test.com",
        }));

        _subject = _mocker.CreateInstance<SignMyController>();
    }

where the class is

public sealed record MyOptions
{
    public string Email{ get; init; } = string.Empty;
}

[Keboo]

@laura-lucciola-exclaimer I am moving your issue to #412 since I believe it is a different issue.