You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the current version in master of this repo accepts an optional cfg parameter however installing latest nuget package (5.0.0.0) it lacks the cfg parameter.
public static void LoadMapsFromAssemblies(params Assembly[] assemblies);
public static void LoadMapsFromAssemblyContainingTypeAndReferencedAssemblies<TType>(Func<AssemblyName, bool> assemblyFilter = null);
public static void LoadMapsFromCallerAndReferencedAssemblies(Func<AssemblyName, bool> assemblyFilter = null);
This is an incredibly useful addition for trying to incorporate heroicautomapper into an existing solution that has hundreds of existing maps as only one call to Mapper.Initialize is allowed.
The text was updated successfully, but these errors were encountered:
I noticed that the current version in master of this repo accepts an optional cfg parameter however installing latest nuget package (5.0.0.0) it lacks the cfg parameter.
In master
In 5.0.0.0 nuget package
This is an incredibly useful addition for trying to incorporate heroicautomapper into an existing solution that has hundreds of existing maps as only one call to Mapper.Initialize is allowed.
The text was updated successfully, but these errors were encountered: