Config generator emits uncompilable code for certain type conflicts

[stephentoub]

The implementation does name mangling, but those mangled names can conflict with other names, e.g.

using Microsoft.Extensions.Configuration;

IConfiguration configuration = new ConfigurationBuilder().Build();

var c1 = new Cint();
var c2 = new C<int>();
configuration.Bind(c1);
configuration.Bind(c2);

internal class C<T>
{
    public int Value { get; set; }
}

internal class Cint
{
    public int Value { get; set; }
}

Tagging subscribers to this area: @dotnet/area-extensions-configuration
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The implementation does name mangling, but those mangled names can conflict with other names, e.g.

using Microsoft.Extensions.Configuration;

IConfiguration configuration = new ConfigurationBuilder().Build();

var c1 = new Cint();
var c2 = new C<int>();
configuration.Bind(c1);
configuration.Bind(c2);

internal class C<T>
{
    public int Value { get; set; }
}

internal class Cint
{
    public int Value { get; set; }
}

Author:	stephentoub
Assignees:	-
Labels:	area-Extensions-Configuration
Milestone:	-

[layomia]

I'll resolve with a shared abstraction doing whatever JSON does here.

[layomia]

Inlining this scenario from #90969:

---

e.g.

namespace S1
{
    class C1
    {
        public void M(IConfiguration configuration)
        {
            var c = new C1();
            configuration.Bind(c);
        }
    }
}
namespace S2
{
    class C1
    {
        public void M(IConfiguration configuration)
        {
            var c = new C1();
            configuration.Bind(c);
        }
    }
}

results in lots of errors like:

error CS0111: Type 'BindingExtensions' already defines a member called 'Bind_C1' with the same parameter types