I found your compact version very useful and understandable. The only thing, which I find a bit magic, are the patterns. But that’s always the point with “convention over configuration”. You have to put somewhere the logic. So, I have to study this pattern stuff and a blog post of you would be also a great help.

Thank you again for your feedback and I hope I will have the chance again the pleasure in future.

var patternsAppliers = new CoolPatternsAppliersHolder(orm);
var mapper = new Mapper(orm, patternsAppliers);
mapper.SetAllPropertiesAndReferencesAsNotNullable();
mapper.Customize(cm => cm.Collection(o => o.Items, x => x.Lazy(CollectionLazy.NoLazy)));
mapper.Customize(cm => cm.ManyToOne(x => x.Order, m => m.Fetch(FetchMode.Join)));

return mapper.CompileMappingFor(allEntities);
}

public static class ConfORMMapperExtension
{
public static void SetAllPropertiesAndReferencesAsNotNullable(this Mapper mapper)
{
mapper.AddPropertyPattern(mi=> true, pm=> pm.NotNullable(true));
mapper.AddManyToOnePattern(mi=> true, mtom=> mtom.NotNullable(true));
}
}

It is an active choice not to implement mocking of abstract and concrete classes, to promote a code against interfaces, not implementations development style. Mocking parts of an implementation, which is what you do when you mock specific methods of an abstract or concrete class adds complexity and is not as clear as mocking an interface.

Simple.Mocking is something I developed when me and the team I worked with at the moment didnt find any mocking framework we were really satisfied with. I will continue to correct bugs and maybe add some functionality but I will strive to keep the API small and simple but still useable.

Greetings
Ivi