Using Profiles in Automapper to map the same types with different logic

by

Profiles are for segregating common configuration applied across several type maps, like formatting. However, type maps are still global. You’re better off creating separate Configuration objects, and creating a separate MappingEngine for each. The Mapper class is merely a static facade over each of those, with some lifecycle management.

More Related Contents:

  1. Ignore mapping one property with Automapper
  2. How to set up Automapper in ASP.NET Core
  3. Automapper: Update property values without creating a new object
  4. AutoMapper convert from multiple sources
  5. How to ignore null values for all source members during mapping in Automapper 6?
  6. AutoMapper vs ValueInjecter [closed]
  7. Copy object to object (with Automapper ?)
  8. Possible to use AutoMapper to map one object to list of objects?
  9. Simple Automapper Example
  10. Dictionary map to an object using Automapper
  11. How to specify mapping rule when names of properties differ
  12. NuGet Package Manager: ‘AutoMapper’ already has a dependency defined for ‘Microsoft.CSharp’
  13. Automapper: Ignore on condition of
  14. Skip null values with custom resolver
  15. Pass Objects to AutoMapper Mapping
  16. Allow mapping of dynamic types using AutoMapper or similar?
  17. AutoMapper Migrating from static API
  18. Add new text to label [closed]
  19. Find all controls in WPF Window by type
  20. How to split csv whose columns may contain ,
  21. Making a control transparent
  22. How can I compare (directory) paths in C#?
  23. How to run unit tests (MSTest) in parallel?
  24. Passing Arrays by Value and by Reference
  25. Azure AD B2C – Role management [duplicate]
  26. Top level domain from URL in C#
  27. What is the use of `default` keyword in C#?
  28. How to make two-way binding on Blazor component
  29. How to set json serializer settings in asp.net core 3?
  30. C# multidimensional arrays iteration

Leave a Comment