github AutoMapper/AutoMapper v5.2.0
5.2.0

latest releases: v13.0.1, v13.0.0, v12.0.1...
7 years ago

As part of this release we had 74 issues closed.

Features

Improvements

  • #1809 Check the destination type override to be a derived type
  • #1753 Expose the destination member
  • #1746 Make IncludeBase work with ReverseMap
  • #1745 Add .editorconfig
  • #1743 ReverseMap ignores mapping inheritance (AutoMapper 5.1.1)
  • #1734 Compile once
  • #1719 Add some helpful casts
  • #1714 Always map array contents & remove the primitive array mapper.
  • #1687 Make it easier to spot missing services
  • #1677 Lazily create convert expressions
  • #1655 UWP 5.2.2 + AutoMapper 5.1.1 = Insanely long builds
  • #1628 Match by name; the member type can be generic and so the types won't …
  • #1624 InvalidOperaionException when automapping using open generics and including the source in a ForMember statement
  • #1530 Make constructor mapping a little more lenient
  • #1528 Invalid constructor mappings throw exceptions at seal-time

Bugs

  • #1814 Filtering dynamic assemblies
  • #1812 Applying partially trusted callers only for full .NET
  • #1806 Catch NRE in MapFrom with value types; fixes #1798
  • #1805 Return null when mapping from null string to nullable
  • #1804 string -> int? conversion returning 0 rather than null
  • #1798 In AutoMapper 5.1.1 MapFrom method does not ignore Null Reference Exception but throws it
  • #1788 Checking for closures (constant expressions) when mapping expressions
  • #1785 Fixing expression visitors to properly visit the underlying expressio…
  • #1778 MapFrom variable 'src' of type 'Xyz' referenced from scope '', but it is not defined
  • #1774 Mapping from "string" to "nullable enum" throws exception
  • #1772 Map string to nullable enum
  • #1765 Fix #1482
  • #1764 MapFrom/ResolveUsing no longer support null assignment
  • #1752 Consider VB closures
  • #1748 Paramterized mappings not working using VB.NET and Profiles
  • #1740 Mapping to/from object doesn't seem useful
  • #1731 Bugfix #1727
  • #1727 Automapper v5.1.1 does not work with ObservableDictionary where Automapper 4 does
  • #1718 When we map a nullable, we should map the underlying type unless an e…
  • #1717 Mapping from nullable enum stopped working in AutoMapper 5
  • #1711 Multiple IEnumerable interfaces
  • #1697 AddProfiles Blows Up With NotSupportedException if Any of the Assemblies are Dynamic
  • #1692 Fixed memory leaks
  • #1691 ConcurrentBag causes memory leak
  • #1685 MethodAccessException: Windows Phone 8.1 (WinRT)
  • #1672 Not needed code - nullables
  • #1664 Differentiation between type and nullable type
  • #1662 Get the element type from the destination object itself
  • #1656 Creating a map for collections throws when destination items of derived type
  • #1654 Short-circuit evaluation
  • #1651 Complex flattening
  • #1649 Convert the null substitute to what's needed for projections
  • #1645 Dictionary mappings no longer handle non-empty dictionary destinations in 5.1.1
  • #1642 Convert to nullable
  • #1641 Different ProjectUsings for nullable and non-nullable ints
  • #1638 Decimal to nullable decimal
  • #1635 Call the condition after setting the source property value because it…
  • #1634 Conditions do not get either Source or Destination values
  • #1632 Just clear the destination everytime we don't create it ourselves
  • #1631 NullReferecnceException when flattening values
  • #1630 Mapping onto existing object does no longer clear existing items from List [5.1.1]
  • #1626 Don't hard code the ToString call, use the StringMapper; remove the t…
  • #1620 Mapping object to string fails with NullReferenceException when called on null.
  • #1618 Profile.AllowNullCollections ignored?
  • #1617 Error when mapping an expression containing a (non-parameter) instance of the mapped type
  • #1607 IMemberValueResolver is created and called twice
  • #1482 UseAsDataSource Translate constants with PropertyMap changes.
  • #1008 UseAsDataSource() - filtering by date in OData query results in mapping exception
  • #882 UseDataSource() with property-path expression leads to exception

Where to get it

You can download this release from nuget

Don't miss a new AutoMapper release

NewReleases is sending notifications on new releases.