Skip to content

Releases: AutoMapper/AutoMapper

3.1.1

31 Dec 02:23
Compare
Choose a tag to compare

Maintenance release:

  • Mapping of IList properties map as reference #428
  • Bug in Install.ps1 - method Where not found #418

This fixes bugs introduced in v3.1.0.

Full list of closed issues
Full list of changes

3.1.0

21 Nov 03:50
Compare
Choose a tag to compare

AutoMapper expands its Portable Class Library support to include Xamarin. AutoMapper 3.1 supports the following runtimes:

  • .NET 4 and higher
  • Silverlight 5
  • Windows Phone 8
  • .NET for Windows Store apps (WinRT)
  • Xamarin.iOS
  • Xamarin.Android

Full list of closed issues
Full list of changes

Enhancements

  • Sharing base type mappings between derived types #309
  • Added possibility to disable constructor mapping for a profile #401
  • Extremely slow with large arrays #390
  • Revamped API for custom object mappers #385
  • Support array types in LINQ queries #375
  • AutoMapper now signed (again) #373
  • Support for MonoTouch #372
  • Support for MonoDroid #371
  • Supporting custom expressions for child members in LINQ queries #366
  • Automatic support of Enumerable/Queryable extension methods (Count() etc) #365
  • Complete support for inheriting parent mappings, for multiple children #348, #339, #329, #315, #307
  • Add Items bag to CreateMap and Map options #322
  • Supporting child containers for MappingEngine instance #320

Bug Fixes

  • PCL installation when used in a base project #318 and others
  • Cast exceptions for nullable types #332
  • Concurrency problems in WP8 #394
  • Bug in TypeInfo with inherited fields #386
  • Removed swallowing of exceptions #122

3.0.0

25 Aug 19:15
Compare
Choose a tag to compare

AutoMapper is now a Portable Class Library (PCL) to target multiple platforms including:

  • .NET 4 and higher
  • Silverlight 4 and higher
  • Windows Phone 7.5 and higher
  • .NET for Windows Store apps (WinRT)

Quite a bit of under-the-covers refactoring was needed to convert to a PCL, which should make it easier to have cross-platform support going forward.

New features:

  • Cross platform support
  • Code comments for public API
  • Collection, MapFrom and flattening support in LINQ projection

Issues closed:

  • Automapper: complex nested collections mapping with Entity Framework #360
  • AutoMapper uses Expression.Invoke when Entity Framework does not support it. #358
  • FileNotFoundException in PCL on WinRT App #353
  • Different destination instance using Mapper.Map<TSource, TDestination> with CreateMissingTypeMaps option #352
  • AutoMapper QueryableExtensions throws NullReference #351
  • MappingEngine.CreateMapExpression #347
  • Release notes / Change log for project #346 (hardy-har-har)
  • Cannot project array type #344
  • Entity Framework 5.0 + Project() = Null reference #343
  • Edited QueryableExtensions so that it handles OrderBy and ThenBy on child collections. #327
  • Fixed projection with null reference or null collection in source object. #310
  • CreateMapExpression MapFrom problem #299