Skip to main content

Migrating old AutoMapper codes to 4.2 version with instance based approach

In AutoMapper 4.2 version, static implementation is removed with instance approach. It could be a nightmare to migrate the codes to the newer version with instance approach. I will be putting up guide for migrating codes from the older version to instance approach if someone has used Profile based approach.

Previous implementation (old implementation)

Profile based implementation mapping

 public class UserProfileMapping  
      : Profile  
 {  
      protected override void Configure()  
      {  
           Mapper.CreateMap<UserProfile, PreferenceViewModel>()  
             .ForMember(vm => vm.UserId, m => m.MapFrom(profile => profile.Id));  
      }  
 }  

Single class for registering all AutoMapper configuration

 public static class AutoMapperConfiguration  
 {  
      public static void Configure()  
      {  
           Mapper.Initialize(cfg =>  
           {  
                cfg.AddProfile(new UserProfileMapping());  
           });  
      }  
 }  

The global mapping initialization under global.asax

 AutoMapperConfiguration.Configure();  

Usage under controllers

 var dbUserProfile = // call for getting info from DB.  
 var preference = new PreferenceViewModel();  
 Mapper.Map(dbUserProfile, preference);  

Automapper Queryable Extensions implementation

 var dbQuery = // Db call  
 dbQuery.Project().To<PreferenceViewModel>()  


These above processes were old approach with static methods calls.
In the newer version, there has to be instance based approach, the biggest advantage is dependency injection. I am hoping the API would improve and with this new move someone can create a standard for Mapping the domain models and view models later.


AutoMapper new implementation based on instance approach

Let's start with the order that I followed with the older approach. I will be using constructor dependency injection to wire the whole process.

Profile based implementation mapping

 public class UserProfileMapping   
      : Profile  
 {    
      private readonly IMapperConfiguration MappingConfiguration;  
      public UserProfileMapping(IMapperConfiguration config)  
      {  
           MappingConfiguration = config;  
      }  
      protected override void Configure()  
      {  
           MappingConfiguration  
                .CreateMap<UserProfile, PreferenceViewModel>()  
                .ForMember(vm => vm.UserId, m => m.MapFrom(profile => profile.Id));  
      }  
 }  

The IMapperConfiguration is a new interface for mapping models which we would be checking at a later stage.

Single class for registering all AutoMapper configuration

 public class AutoMapperConfiguration  
 {  
      public AutoMapperConfiguration(IMapperConfiguration mapperConfiguration)  
      {  
           Configure(mapperConfiguration);  
      }  
      public void Configure(IMapperConfiguration mapperConfiguration)  
      {  
           mapperConfiguration.AddProfile(new UserProfileMapping(mapperConfiguration));  
      }  
 }  

If you check changes, the static declaration is removed from class and function both. Implementation is also changed based on dependency injection.


Dependency injection initialization through Ninject (The global mapping initialization under global.asax)

I am including possible mappings which may depend based on application. You can choose based on need.

 // AutoMapper mapping  
 kernel.Bind<MapperConfiguration>()  
       .ToSelf()  
       .InRequestScope()  
       .WithConstructorArgument<Action<IMapperConfiguration>>(  
             cfg => new AutoMapperConfiguration(cfg));  
 kernel.Bind<IConfigurationProvider>().ToMethod(ctx => ctx.Kernel.Get<MapperConfiguration>());  
 kernel.Bind<IMapper>().ToMethod(maper => kernel.Get<MapperConfiguration>().CreateMapper()).InSingletonScope();  
 kernel.Bind<IExpressionBuilder>().ToConstructor(ctx => new ExpressionBuilder(kernel.Get<MapperConfiguration>()));  

The MapperConfiguration has Action<IMapperConfiguration> type constructor parameter. In this, the anonymous action is created and IMapperConfiguration is created to be passed as a parameter for AutoMapperConfiguration .

The other key point is the creation of IMapper implementation instance through CreateMapper() method. This IMapper will be passed across all application to consume mappings.

IConfigurationProvider and IExpressionBuilder can be used for projecting LINQ queries to targetted mapped model.

Usage under controllers

In the controllers, the constructor parameters are taking care of instances  for mappers. Mainly, IMapper is used of mapping objects.

 public class AccountController  
      : Controller  
 {  
      private readonly IMapper Mapper;  
      public AccountController(IMapper modelMapper)  
      {  
           // Initialization codes  
      }  
      public ActionResult UserPreference()  
      {  
           var dbUserProfile = // call for getting info from DB.   
           var preference = new PreferenceViewModel();   
           Mapper.Map(dbUserProfile, preference);   
           // Code  
      }  
 }  


Automapper Queryable Extensions implementation

For extension method ideally, IExpressionBuilder needs to be used for LINQ projection but due to some issue or incompatibilty with QueryableExtensions, I am using IConfigurationProvider to do projection.

 public class AccountController  
      : Controller  
 {  
      private readonly IConfigurationProvider ConfigurationProvider;  
      public AccountController(IMapper modelMapper,  
           IConfigurationProvider configurationProvider)  
      {  
           // Initialization codes  
      }  
      public ActionResult UserPreference()  
      {  
           var dbQuery = // Db call   
           var res = dbQuery.ProjectTo<PreferenceViewModel>(ConfigurationProvider)   
           // Code  
      }  
 }  



Comments

Popular posts from this blog

Data seed for the application with EF, MongoDB or any other ORM.

Most of ORMs has moved to Code first approach where everything is derived/initialized from codes rather than DB side. In this situation, it is better to set data through codes only. We would be looking through simple technique where we would be Seeding data through Codes. I would be using UnitOfWork and Repository pattern for implementing Data Seeding technique. This can be applied to any data source MongoDB, EF, or any other ORM or DB. Things we would be doing. - Creating a base class for easy usage. - Interface for Seed function for any future enhancements. - Individual seed classes. - Configuration to call all seeds. - AspNet core configuration to Seed data through Seed configuration. Creating a base class for easy usage public abstract class BaseSeed<TModel> where TModel : class { protected readonly IMyProjectUnitOfWork MyProjectUnitOfWork; public BaseSeed(IMyProjectUnitOfWork MyProjectUnitOfWork) { ...

Making FluentValidation compatible with Swagger including Enum or fixed List support

FluentValidation is not directly compatible with Swagger API to validate models. But they do provide an interface through which we can compose Swagger validation manually. That means we look under FluentValidation validators and compose Swagger validator properties to make it compatible. More of all mapping by reading information from FluentValidation and setting it to Swagger Model Schema. These can be done on any custom validation from FluentValidation too just that proper schema property has to be available from Swagger. Custom validation from Enum/List values on FluentValidation using FluentValidation.Validators; using System.Collections.Generic; using System.Linq; using static System.String; /// <summary> /// Validator as per list of items. /// </summary> /// <seealso cref="PropertyValidator" /> public class FixedListValidator : PropertyValidator { /// <summary> /// Gets the valid items /// <...

Elegantly dealing with TimeZones in MVC Core / WebApi

In any new application handling TimeZone/DateTime is mostly least priority and generally, if someone is concerned then it would be handled by using DateTime.UtcNow on codes while creating current dates and converting incoming Date to UTC to save on servers. Basically, the process is followed by saving DateTime to UTC format in a database and keep converting data to native format based on user region or single region in the application's presentation layer. The above is tedious work and have to be followed religiously. If any developer misses out the manual conversion, then that area of code/view would not work. With newer frameworks, there are flexible ways to deal/intercept incoming or outgoing calls to simplify conversion of TimeZones. These are steps/process to achieve it. 1. Central code for storing user's state about TimeZone. Also, central code for conversion logic based on TimeZones. 2. Dependency injection for the above class to ...

Centralized model validation both for MVC/WebApi and SPA client-side validation using FluentValidation

Validation is one of the crucial parts of any application. It has to validate on both client side and server side requests. What are target features or implementation from this article? Model validation for any given model. Centralized/One code for validation on both server-side and client-side. Automatic validation of model without writing any extra codes on/under actions for validation.  NO EXTRA/ANY codes on client-side to validate any form. Compatible with SPA. Can be compatible with any client-side validation framework/library. Like Angular Reactive form validation or any jquery validation libraries. Tools used in the implementation? FluentValidation : I feel DataAnnotation validation are excellent and simple to use, but in case of complex validation or writing any custom validations are always tricker and need to write a lot of codes to achieve whereas FluentValidations are simple even in case of complex validation. Generally, we need to validate inc...

Handling JSON DateTime format on Asp.Net Core

This is a very simple trick to handle JSON date format on AspNet Core by global settings. This can be applicable for the older version as well. In a newer version by default, .Net depends upon Newtonsoft to process any JSON data. Newtonsoft depends upon Newtonsoft.Json.Converters.IsoDateTimeConverter class for processing date which in turns adds timezone for JSON data format. There is a global setting available for same that can be adjusted according to requirement. So, for example, we want to set default formatting to US format, we just need this code. services.AddMvc() .AddJsonOptions(options => { options.SerializerSettings.DateTimeZoneHandling = "MM/dd/yyyy HH:mm:ss"; });

Kendo MVC Grid DataSourceRequest with AutoMapper

Kendo Grid does not work directly with AutoMapper but could be managed by simple trick using mapping through ToDataSourceResult. The solution works fine until different filters are applied. The problems occurs because passed filters refer to view model properties where as database model properties are required after AutoMapper is implemented. So, the plan is to intercept DataSourceRequest  and modify names based on database model. To do that we are going to create implementation of  CustomModelBinderAttribute to catch calls and have our own implementation of DataSourceRequestAttribute from Kendo MVC. I will be using same source code from Kendo but will replace column names for different criteria for sort, filters, group etc. Let's first look into how that will be implemented. public ActionResult GetRoles([MyDataSourceRequest(GridId.RolesUserGrid)] DataSourceRequest request) { if (request == null) { throw new Argume...

Channel, ChannelReader and ChannelWriter to manage data streams in multi-threading environment

I came across Channel class while working with SignalR which looks really interesting. By looking into NuGet packages ( https://www.nuget.org/packages/System.Threading.Channels ), it seems just 4 months old. The Channel class provides infrastructure to have multiple reads and write simuletensely through it's Reader and Writer properties. This is where it is handy in case of SignalR where data streaming needs to be done but is not just limited to that but wherever something needs to be read/write/combination of both in a multi-threading environment. In my case with SignalR, I had to stream stock data at a regular interval of time. public ChannelReader<StockData> StreamStock() { var channel = Channel.CreateUnbounded<StockData>(); _stockManager.OnStockData = stockData => { channel.Writer.TryWrite(stockData); }; return channel.Reader; } The SignalR keeps return type of ChannelReader<StockData> open so that whatev...

LDAP with ASP.Net Identity Core in MVC with project.json

Lightweight Directory Access Protocol (LDAP), the name itself explain it. An application protocol used over an IP network to access the distributed directory information service. The first and foremost thing is to add references for consuming LDAP. This has to be done by adding reference from Global Assembly Cache (GAC) into project.json "frameworks": { "net461": { "frameworkAssemblies": { "System.DirectoryServices": "4.0.0.0", "System.DirectoryServices.AccountManagement": "4.0.0.0" } } }, These  System.DirectoryServices  and  System.DirectoryServices.AccountManagement  references are used to consume LDAP functionality. It is always better to have an abstraction for irrelevant items in consuming part. For an example, the application does not need to know about PrincipalContext or any other dependent items from those two references to make it extensible. So, we can begin wi...

Trim text in MVC Core through Model Binder

Trimming text can be done on client side codes, but I believe it is most suitable on MVC Model Binder since it would be at one place on infrastructure level which would be free from any manual intervention of developer. This would allow every post request to be processed and converted to a trimmed string. Let us start by creating Model binder using Microsoft.AspNetCore.Mvc.ModelBinding; using System; using System.Threading.Tasks; public class TrimmingModelBinder : IModelBinder { private readonly IModelBinder FallbackBinder; public TrimmingModelBinder(IModelBinder fallbackBinder) { FallbackBinder = fallbackBinder ?? throw new ArgumentNullException(nameof(fallbackBinder)); } public Task BindModelAsync(ModelBindingContext bindingContext) { if (bindingContext == null) { throw new ArgumentNullException(nameof(bindingContext)); } var valueProviderResult = bindingContext.ValueProvider.GetValue(bin...

Kendo MVC Grid DataSourceRequest with AutoMapper - Advance

The actual process to make DataSourceRequest compatible with AutoMapper was explained in my previous post  Kendo MVC Grid DataSourceRequest with AutoMapper , where we had created custom model binder attribute and in that property names were changed as data models. In this post we will be looking into using AutoMapper's Queryable extension to retrieve the results based on selected columns. When  Mapper.Map<RoleViewModel>(data)  is called it retrieves all column values from table. The Queryable extension provides a way to retrieve only selected columns from table. In this particular case based on properties of  RoleViewModel . The previous approach that we implemented is perfect as far as this article ( 3 Tips for Using Telerik Data Access and AutoMapper ) is concern about performance where it states: While this functionality allows you avoid writing explicit projection in to your LINQ query it has the same fatal flaw as doing so - it prevents the qu...