Skip to main content

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 query result from being cached.
Since this can have a strong negative impact on the performance even though only minimal amount of data is retrieved, we advise you not to use AutoMapper projection in LINQ queries. Instead we recommend you map the instances of your persistent types after they have been completely retrieved in memory using the Map method of AutoMapper.
I am not against or in favour of any approach it all depends on requirement. If we have tables with large number of columns then it won't be good approach. So, if you plan to go with AutoMapper extension for projection then only follow ahead.

ToDataSourceResult is an extension method from Kendo, which internally takes care of projection with different sorts, filters, groups and aggregates. We need all these features except the projection that need to handled by us using AutoMapper. The ToDataSourceResult uses "Kendo.Mvc.Extensions.CreateDataSourceResult" function to form mentioned features. 

This is a only part of code that we need to implement for having AutoMapper Linq Projection:

     /// <summary>  
     /// Creates the data source result.  
     /// </summary>  
     /// <typeparam name="TModel">The type of the model.</typeparam>  
     /// <typeparam name="TResult">The type of the result.</typeparam>  
     /// <param name="queryable">The queryable.</param>  
     /// <param name="request">The request.</param>  
     /// <returns>Kendo Data source result</returns>  
     /// <remarks>MODIFICATION OF "Kendo.Mvc.Extensions.CreateDataSourceResult" TO IMPLEMENT AUTOMAPPER PROJECTION.</remarks>  
     public static DataSourceResult CreateDataSourceResult<TModel, TResult>(this IQueryable<TModel> queryable, DataSourceRequest request)  
     {  
       Func<AggregateDescriptor, IEnumerable<AggregateFunction>> aggregates = null;  
       var dataSourceResult = new DataSourceResult();  
       IQueryable queryables = queryable;  
       var filterDescriptors = new List<IFilterDescriptor>();  
       if (request.Filters != null)  
       {  
         filterDescriptors.AddRange(request.Filters);  
       }  
       if (filterDescriptors.Any<IFilterDescriptor>())  
       {  
         queryables = queryables.Where(filterDescriptors);  
       }  
       var sortDescriptors = new List<SortDescriptor>();  
       if (request.Sorts != null)  
       {  
         sortDescriptors.AddRange(request.Sorts);  
       }  
       var sortDescriptors1 = new List<SortDescriptor>();  
       var groupDescriptors = new List<GroupDescriptor>();  
       if (request.Groups != null)  
       {  
         groupDescriptors.AddRange<GroupDescriptor>(request.Groups);  
       }  
       var aggregateDescriptors1 = new List<AggregateDescriptor>();  
       if (request.Aggregates != null)  
       {  
         aggregateDescriptors1.AddRange(request.Aggregates);  
       }  
       if (aggregateDescriptors1.Any<AggregateDescriptor>())  
       {  
         IQueryable queryables1 = queryables.AsQueryable();  
         IQueryable queryables2 = queryables1;  
         if (filterDescriptors.Any<IFilterDescriptor>())  
         {  
           queryables2 = queryables1.Where(filterDescriptors);  
         }  
         dataSourceResult.AggregateResults = queryables2.Aggregate(aggregateDescriptors1.SelectMany<AggregateDescriptor, AggregateFunction>((AggregateDescriptor a) => a.Aggregates));  
         if (groupDescriptors.Any<GroupDescriptor>() && aggregateDescriptors1.Any<AggregateDescriptor>())  
         {  
           groupDescriptors.Each<GroupDescriptor>((GroupDescriptor g) =>  
           {  
             AggregateFunctionCollection aggregateFunctions = g.AggregateFunctions;  
             List<AggregateDescriptor> aggregateDescriptors = aggregateDescriptors1;  
             if (aggregates == null)  
             {  
               aggregates = (AggregateDescriptor a) => a.Aggregates;  
             }  
             aggregateFunctions.AddRange<AggregateFunction>(aggregateDescriptors.SelectMany<AggregateDescriptor, AggregateFunction>(aggregates));  
           });  
         }  
       }  
       dataSourceResult.Total = queryables.Count();  
       if (groupDescriptors.Any<GroupDescriptor>())  
       {  
         groupDescriptors.Reverse<GroupDescriptor>().Each<GroupDescriptor>((GroupDescriptor groupDescriptor) =>  
         {  
           SortDescriptor sortDescriptor3 = new SortDescriptor()  
           {  
             Member = groupDescriptor.Member,  
             SortDirection = groupDescriptor.SortDirection  
           };  
           sortDescriptors.Insert(0, sortDescriptor3);  
           sortDescriptors1.Add(sortDescriptor3);  
         });  
       }  
       if (sortDescriptors.Any<SortDescriptor>())  
       {  
         queryables = queryables.Sort(sortDescriptors);  
       }  
       IQueryable queryables3 = queryables;  
       queryables = queryables.Page(request.Page - 1, request.PageSize);  
       if (groupDescriptors.Any<GroupDescriptor>())  
       {  
         queryables = queryables.GroupBy(queryables3, groupDescriptors);  
       }  
       dataSourceResult.Data = (queryables as IQueryable<TModel>).Execute<TModel, TResult>();  
       sortDescriptors1.Each<SortDescriptor>((SortDescriptor sortDescriptor) => sortDescriptors.Remove(sortDescriptor));  
       return dataSourceResult;  
     }  
     /// <summary>  
     /// Executes the specified source.  
     /// </summary>  
     /// <typeparam name="TModel">The type of the model.</typeparam>  
     /// <typeparam name="TResult">The type of the result.</typeparam>  
     /// <param name="source">The source.</param>  
     /// <returns></returns>  
     /// <exception cref="System.ArgumentNullException">source</exception>  
     /// <remarks>MODIFICATION OF "Kendo.Mvc.Extensions.Execute" TO IMPLEMENT AUTOMAPPER PROJECTION.</remarks>  
     private static IEnumerable Execute<TModel, TResult>(this IQueryable<TModel> source)  
     {  
       if (source == null)  
       {  
         throw new ArgumentNullException("source");  
       }  
       Type elementType = source.ElementType;  
       if (elementType != typeof(AggregateFunctionsGroup))  
       {  
         return source.Project().To<TResult>();  
       }  
       // TODO: Need to test with grouping  
       List<AggregateFunctionsGroup> aggregateFunctionsGroups = new List<AggregateFunctionsGroup>();  
       foreach (AggregateFunctionsGroup aggregateFunctionsGroup in source as IQueryable)  
       {  
         var aggregateQuerable = aggregateFunctionsGroup.Items.AsQueryable() as IQueryable<TModel>;  
         if (aggregateQuerable != null)  
         {  
           aggregateFunctionsGroup.Items = aggregateQuerable.Execute<TModel, TResult>();  
           aggregateFunctionsGroups.Add(aggregateFunctionsGroup);  
         }  
       }  
       return aggregateFunctionsGroups;  
     }  

If we see above code we only have two functions but both of them are having same code as whatever Kendo is providing with very few changes. The CreateDataSourceResult function is responsible for different sorts, filters, groups and aggregates but the actual call is happening under Execute function. To implement AutoMapper Linq Projection we only needed to modify Execute function but since it is only through CreateDataSourceResult, we need to modify both.

This is return source.Project().To<TResult>(); only change done under Execute function for mapping.

NOTE: I have not tested it with grouping. Possibly that might be the reason, Kendo did not provided some kind injection for mapping.

After that being setup we only need to call in this way.

 queryable.CreateDataSourceResult<RoleDomainModel, RoleViewModel>(request)  
 // Another example
 UnitOfWork.RoleRepository.All().CreateDataSourceResult<RoleDomainModel, RoleViewModel>(request);  

If you want, we can have similar implementation like Kendo by creating our own version of extension method ToDataSourceResult which can consume our created functions.


Popular posts from this blog

Architecture solution composting Repository Pattern, Unit Of Work, Dependency Injection, Factory Pattern and others

Project architecture is like garden, we plant the things in certain order and eventually they grow in similar manner. If things are planted well then they will all look(work) great and easier to manage. If they grow as cumbersome it would difficult to maintain and with time more problems would be happening in maintenance.

There is no any fixed or known approach to decide project architecture and specially with Agile Methodology. In Agile Methodology, we cannot predict how our end products will look like similarly we cannot say a certain architecture will fit well for entire development lifespan for project. So, the best thing is to modify the architecture as per our application growth. I understand that it sounds good but will be far more problematic with actual development. If it is left as it is then more problems will arise with time. Just think about moving plant vs a full grown tree.

Coming to technical side, In this article, I will be explaining about the various techniques tha…

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 with some bas…

Configuring Ninject, Asp.Net Identity UserManager, DataProtectorTokenProvider with Owin

It can be bit tricky to configure both Ninject and Asp.Net Identity UserManager if some value is expected from DI to configure UserManager. We will look into configuring both and also use OwinContext to get UserManager.

As usual, all configuration need to be done on Startup.cs. It is just a convention but can be used with different name, the important thing is to decorate class with following attribute to make it Owin start-up:

[assembly: OwinStartup(typeof(MyProject.Web.Startup))]
Ninject configuration

Configuring Ninject kernel through method which would be used to register under Owin.

Startup.cs
public IKernel CreateKernel() { var kernel = new StandardKernel(); try { //kernel.Bind<IHttpModule>().To<HttpApplicationInitializationHttpModule>(); // TODO: Put any other injection which are required. return kernel; } catch { kernel.Dispose(); throw; }…