AllowNullCollections has no effect when a profile is used

When a mapper configuration is set through a profile, the AllowNullCollections setting has no effect. The following pseudo test fails:

public class Source
{
    public System.Collections.Generic.IList<string> Collection { get; set; }
}

public class Destination
{
    public System.Collections.Generic.IList<string> Collection { get; set; }
}

public class TestProfile: AutoMapper.Profile
{
    protected override void Configure()
    {
        CreateMap<Source, Destination>();
    }
}

[Fact]
public void NullCollection()
{
    var mapper = new MapperConfiguration(cfg => {
        cfg.AllowNullCollections=true;
        cfg.AddProfile<TestProfile>();
    }).CreateMapper();
    var source = new Source();

    Destination destination = mapper.Map<Destination>(source);

    Assert.Null(destination.Collection);
}

When configured directly with CreateMap, the setting works as expected.

AutoMapper 4.2.1

[engenb]

I am seeing this issue, possibly a regression, in version 5.1.1.

The following unit test fails

[Fact]
public void Test()
{
    var config = new MapperConfiguration(configure =>
    {
        configure.AddProfile<TestProfile>();
    });

    config.AssertConfigurationIsValid();
    var mapper = config.CreateMapper();

    var source = new Source();

    var result = mapper.Map<Destination>(source);

    Assert.Null(result.Dictionary);
}

public class Source
{
    public IDictionary<string, string> Dictionary { get; set; }
}

public class Destination
{
    public IDictionary<string, string> Dictionary { get; set; }
}

public class TestProfile : Profile
{
    public TestProfile()
    {
        AllowNullCollections = true;
        CreateMap<Source, Destination>();
    }
}

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.