Skip to main content

Interface based model binding to populate properties value automatically

Interface is great way to make consistency and re-useability of codes. In this tutorial, I am going to show the power of interface to populate view/domain models automatically and interchange values between models.

Technologies or techniques used in this approach:
- MVC.
- Interface for models.
- MVC model binder for associated model with interface. Through this model binder we will populate values.
- T4 template to generate code to register model binder with all models associated with interface.
- Generic extension method to interchange values.

It might sounding bit complex to achieve small thing. Just hold on with me and see unfolding. This will result in easier maintenance and less repetitive code.

First let's start with creation of Interface that need to be populate automatically. This interface would be implemented on models and values will be auto-populated on binder.

   /// <summary>  
   /// Interface for storing entry related values  
   /// </summary>  
   public interface IAddUpdate  
   {  
     /// <summary>  
     /// Gets or sets the created at.  
     /// </summary>  
     /// <value>The created at.</value>  
     DateTime CreatedAt { get; set; }  
     /// <summary>  
     /// Gets or sets the created by.  
     /// </summary>  
     /// <value>The created by.</value>  
     string CreatedBy { get; set; }  
     /// <summary>  
     /// Gets or sets the updated at.  
     /// </summary>  
     /// <value>The updated at.</value>  
     DateTime? UpdatedAt { get; set; }  
     /// <summary>  
     /// Gets or sets the updated by.  
     /// </summary>  
     /// <value>The updated by.</value>  
     string UpdatedBy { get; set; }  
   }  

After creation of interface we can create our domain and view models by inheriting above interface.

You can have any properties or functionality in the domain model. Just that above interface need to be implemented.

  /// <summary>  
   /// User domain model  
   /// </summary>  
   public class UserModel  
     : IAddUpdate  
   {  
     /// <summary>  
     /// Gets or sets the identifier.  
     /// </summary>  
     /// <value>  
     /// The identifier.  
     /// </value>  
     public int Id { get; set; }  
     /// <summary>  
     /// Gets or sets the user identifier.  
     /// </summary>  
     /// <value>  
     /// The user identifier.  
     /// </value>  
     public string UserId { get; set; }  
     /// <summary>  
     /// Gets or sets the email.  
     /// </summary>  
     /// <value>  
     /// The email.  
     /// </value>  
     public string Email { get; set; }  
     /// <summary>  
     /// Gets or sets the password.  
     /// </summary>  
     /// <value>  
     /// The password.  
     /// </value>  
     public string Password { get; set; }  
     #region " IAddUpdate implementation "  
     /// <summary>  
     /// Gets or sets the created at.  
     /// </summary>  
     /// <value>  
     /// The created at.  
     /// </value>  
     public System.DateTime CreatedAt { get; set; }  
     /// <summary>  
     /// Gets or sets the created by.  
     /// </summary>  
     /// <value>  
     /// The created by.  
     /// </value>  
     public string CreatedBy { get; set; }  
     /// <summary>  
     /// Gets or sets the updated at.  
     /// </summary>  
     /// <value>  
     /// The updated at.  
     /// </value>  
     public System.DateTime? UpdatedAt { get; set; }  
     /// <summary>  
     /// Gets or sets the updated by.  
     /// </summary>  
     /// <value>  
     /// The updated by.  
     /// </value>  
     public string UpdatedBy { get; set; }  
     #endregion " IAddUpdate implementation "  
   }  

View Model creation is in similar way, interface need to be implemented. I have created constructor to initialize default value of created date as current date.

  /// <summary>  
   /// User view model  
   /// </summary>  
   public class UserViewModel  
     : IAddUpdate  
   {  
     /// <summary>  
     /// Initializes a new instance of the <see cref="UserViewModel"/> class.  
     /// </summary>  
     public UserViewModel()  
     {  
       CreatedAt = DateTime.Now;  
     }  
     /// <summary>  
     /// Gets or sets the user identifier.  
     /// </summary>  
     /// <value>  
     /// The user identifier.  
     /// </value>  
     [StringLength(15)]  
     [Required]  
     public string UserId { get; set; }  
     /// <summary>  
     /// Gets or sets the first name.  
     /// </summary>  
     /// <value>  
     /// The first name.  
     /// </value>  
     public string FirstName { get; set; }  
     /// <summary>  
     /// Gets or sets the last name.  
     /// </summary>  
     /// <value>  
     /// The last name.  
     /// </value>  
     public string LastName { get; set; }  
     /// <summary>  
     /// Gets or sets the email.  
     /// </summary>  
     /// <value>  
     /// The email.  
     /// </value>  
     [DataType(DataType.EmailAddress)]  
     public string Email { get; set; }  
     #region " IAddUpdate implementation "  
     /// <summary>  
     /// Gets or sets the created at.  
     /// </summary>  
     /// <value>  
     /// The created at.  
     /// </value>  
     public System.DateTime CreatedAt { get; set; }  
     /// <summary>  
     /// Gets or sets the created by.  
     /// </summary>  
     /// <value>  
     /// The created by.  
     /// </value>  
     public string CreatedBy { get; set; }  
     /// <summary>  
     /// Gets or sets the updated at.  
     /// </summary>  
     /// <value>  
     /// The updated at.  
     /// </value>  
     public System.DateTime? UpdatedAt { get; set; }  
     /// <summary>  
     /// Gets or sets the updated by.  
     /// </summary>  
     /// <value>  
     /// The updated by.  
     /// </value>  
     public string UpdatedBy { get; set; }  
     #endregion " IAddUpdate implementation "  
   }  

Now interface and different model creation is done. Let's look into creation of model binder which will set properties value based on IAddUpdate interface.

  /// <summary>  
   /// Model binding for IAddUpdate interface implemented models  
   /// </summary>  
   public class InterfaceIAddUpdateModelBinder  
     : DefaultModelBinder  
   {  
     /// <summary>  
     /// The Min allowed date  
     /// </summary>  
     private const int MIN_ALLOWED_YEAR = 1800;  
     /// <summary>  
     /// Binds the model by using the specified controller context and binding context.  
     /// </summary>  
     /// <param name="controllerContext">The context within which the controller operates.  
     /// The context information includes the controller, HTTP content, request context, and route data.</param>  
     /// <param name="bindingContext">The context within which the model is bound. The context includes information  
     /// such as the model object, model name, model type, property filter, and value provider.</param>  
     /// <returns>  
     /// The bound object.  
     /// </returns>  
     /// <exception cref="System.ArgumentNullException">  
     /// controllerContext  
     /// or  
     /// bindingContext  
     /// </exception>  
     public override object BindModel(ControllerContext controllerContext, ModelBindingContext bindingContext)  
     {  
       #region " Null checks "  
       if (controllerContext == null)  
       {  
         throw new ArgumentNullException("controllerContext");  
       }  
       if (bindingContext == null)  
       {  
         throw new ArgumentNullException("bindingContext");  
       }  
       if (bindingContext.Model != null)  
       {  
         return bindingContext.Model;  
       }  
       #endregion " Null checks "  
       var model = base.BindModel(controllerContext, bindingContext);  
       var addUpdateModel = model as IAddUpdate;  
       if (addUpdateModel == null)  
       {  
         return model;  
       }  
       // Anonymous function to set values  
       // NOTE: No checks are done as it is expecting same values through interfaces.  
       Action<string, object> setPropertyValue = (propertyName, value) =>  
       {  
         var prop = bindingContext.ModelType.GetProperty(propertyName);  
         prop.SetValue(model, value, null);  
       };  
       // NOTE: Change assignment of values according to your need  
       #region " Set values "  
       if (addUpdateModel.CreatedAt.Year < MIN_ALLOWED_YEAR)  
       {  
         setPropertyValue("CreatedAt", DateTime.Now);  
       }  
       if (String.IsNullOrEmpty(addUpdateModel.CreatedBy))  
       {  
         setPropertyValue("CreatedBy", controllerContext.RequestContext.HttpContext.User.Identity.Name);  
       }  
       if (!addUpdateModel.UpdatedAt.HasValue)  
       {  
         setPropertyValue("UpdatedAt", DateTime.Now);  
       }  
       if (String.IsNullOrEmpty(addUpdateModel.UpdatedBy))  
       {  
         setPropertyValue("UpdatedBy", controllerContext.RequestContext.HttpContext.User.Identity.Name);  
       }  
       #endregion " Set values "  
       return model;  
     }  
   }  

The above model binder will try to check if model is using interface. If model is using IAddUpdate interface then it would populate values according to user identity/principal. These could be customized according to your need.

Our interface, model and binder is set now. Now we need to create T4 template to generate code to register models with InterfaceIAddUpdateModelBinder binder. This will take care of any new models getting associated with IAddUpdate interface.

 // TODO: Change path according to project/folder structure  
 <#@ assembly name="$(SolutionDir)ModelInterface\bin\ModelInterface.Model.dll" #><#@ template debug="true" hostSpecific="true" #>  
 <#@ template language="C#" debug="false" hostspecific="true" #>  
 <#@ output extension=".cs" #>  
 <#@ import namespace="System" #>  
 <#@ import namespace="System.Linq" #>  
 <#@ import namespace="System.Collections" #>  
 <#@ import namespace="System.Reflection" #>  
 <#@ import namespace="System.Collections.Generic" #>   
 <#@ include file="EF.Utility.CS.ttinclude"#>  
 <#  
      CodeGenerationTools code = new CodeGenerationTools(this);  
      // Interface to look for  
      var interfaceType = typeof(ModelInterface.Model.ModelConstraint.IAddUpdate);  
      // Assembly to look under for implementation of above interface  
      var assembly = interfaceType.Assembly;  
 #>  
 using ModelInterface.ModelBinder;  
 using System.Web.Mvc;  
 namespace <#= code.VsNamespaceSuggestion()#>  
 {   
      //------------------------------------------------------------------------------  
      // <auto-generated>  
      //   This code was generated from a template and will be overwritten as soon   
      //       as the template is executed.  
      //  
      //   Changes to this file may cause incorrect behavior and will be lost if  
      //   the code is regenerated.  
      // </auto-generated>  
      //------------------------------------------------------------------------------  
      /// <summary>  
   /// Registers models implementing IAddUpdate interface  
   /// </summary>  
      public static class RegisterIAddUpdateInterface  
      {  
        /// <summary>  
     /// Registers models implementing IAddUpdate interface  
     /// </summary>  
     /// <param name="binder">The binder.</param>  
           public static void RegisterIAddUpdateModels(ModelBinderDictionary binder)  
           {  
                <#  
                foreach (var item in GetInterfaceAssociatedTypes(interfaceType,assembly))  
                {  
                 #>binder.Add(typeof(<#=code.Escape(item.ToString())#>), new InterfaceIAddUpdateModelBinder());  
                 <#  
                }  
           #>  
 }  
      }  
 }  
 <#+  
 // Get all types implementing interface  
 IEnumerable<Type> GetInterfaceAssociatedTypes(Type interfaceType, Assembly assembly)  
 {  
      return (from typ in assembly.GetTypes()  
        where interfaceType.IsAssignableFrom(typ) &&  
                 interfaceType != typ  
        select typ);  
 }  
 #>  

The above T4 template will generate code something similar to below code. Depends upon models.

 using ModelInterface.ModelBinder;  
 using System.Web.Mvc;  
 namespace ModelInterface.App_Start  
 {  
   //------------------------------------------------------------------------------  
   // <auto-generated>  
   //   This code was generated from a template and will be overwritten as soon   
   //       as the template is executed.  
   //  
   //   Changes to this file may cause incorrect behavior and will be lost if  
   //   the code is regenerated.  
   // </auto-generated>  
   //------------------------------------------------------------------------------  
   /// <summary>  
   /// Registers models implementing IAddUpdate interface  
   /// </summary>  
   public static class RegisterIAddUpdateInterface  
   {  
     /// <summary>  
     /// Registers models implementing IAddUpdate interface  
     /// </summary>  
     /// <param name="binder">The binder.</param>  
     public static void RegisterIAddUpdateModels(ModelBinderDictionary binder)  
     {  
       binder.Add(typeof(ModelInterface.Model.DomainModel.UserModel), new InterfaceIAddUpdateModelBinder());  
       binder.Add(typeof(ModelInterface.Model.ViewModel.UserViewModel), new InterfaceIAddUpdateModelBinder());  
     }  
   }  
 }  

We need to pass ModelBinderDictionary to RegisterIAddUpdateModels function for registration of model binding. To do that, in Application_Start event of Global.asax.cs file put this line:

 // Register model binder for IAddUpdate interface implemented models  
 RegisterIAddUpdateInterface.RegisterIAddUpdateModels(ModelBinders.Binders);  

This would set up whole thing. The final touch that we need to do is to have generic function to set up properties value from one object to other.

   /// <summary>  
   /// Type conversion methods  
   /// </summary>  
   public static class TypeConversion  
   {  
     /// <summary>  
     /// Copy values from one object to another implementing <see cref="IAddUpdate"/>  
     /// </summary>  
     /// <typeparam name="TFirstModel">The type of the first model.</typeparam>  
     /// <typeparam name="TSecondModel">The type of the second model.</typeparam>  
     /// <param name="targetModel">The target model.</param>  
     /// <param name="sourceModel">The source model.</param>  
     /// <returns>Changed value model</returns>  
     /// <exception cref="System.ArgumentNullException">  
     /// targetModel  
     /// or  
     /// sourceModel  
     /// </exception>  
     public static TFirstModel ModelConvert<TFirstModel, TSecondModel>(this TFirstModel targetModel,   
       TSecondModel sourceModel)  
       where TFirstModel : IAddUpdate  
       where TSecondModel : IAddUpdate  
     {  
       #region " Null Checks "  
       if (targetModel == null)  
       {  
         throw new ArgumentNullException("targetModel");  
       }  
       if (sourceModel == null)  
       {  
         throw new ArgumentNullException("sourceModel");  
       }  
       #endregion " Null Checks "  
       targetModel.CreatedAt = sourceModel.CreatedAt;  
       targetModel.CreatedBy = sourceModel.CreatedBy;  
       targetModel.UpdatedAt = sourceModel.UpdatedAt;  
       targetModel.UpdatedBy = sourceModel.UpdatedBy;  
       return targetModel;  
     }  
   }  

After changing whole thing let's try up on controller level.

   /// <summary>  
   /// User controller for handling user related operation  
   /// </summary>  
   public class UserController : Controller  
   {  
     /// <summary>  
     /// Indexes this instance.  
     /// </summary>  
     /// <returns></returns>  
     public ActionResult Index()  
     {  
       return View(new UserViewModel());  
     }  
     /// <summary>  
     /// Indexes the specified model.  
     /// </summary>  
     /// <param name="model">The model.</param>  
     /// <returns></returns>  
     [HttpPost]  
     [ValidateAntiForgeryToken]  
     public ActionResult Index(UserViewModel model)  
     {  
       if (!ModelState.IsValid)  
       {  
         return View(model);  
       }  
       var userDomain = new UserModel  
         {  
           Email = model.Email,  
         };  
       // TODO: Save view model's extra properties to different domain model, if needed  
       // Generic extension method for setting up values from one object to another  
       userDomain.ModelConvert(model);  
       // TODO: Check userDomain object while debugging  
       return View(model);  
     }  
   }  

userDomain.ModelConvert(model) will get values from model object and set it to userDomain. If some automapper is used then there is no need of it.


Source code: https://www.dropbox.com/s/0ous4epbz732sr0/ModelInterface.zip

Comments

Popular posts from this blog

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 ...

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 /// <...

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"; });

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 ...

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...

Using Redis distributed cache in dotnet core with helper extension methods

Redis cache is out process cache provider for a distributed environment. It is popular in Azure Cloud solution, but it also has a standalone application to operate upon in case of small enterprises application. How to install Redis Cache on a local machine? Redis can be used as a local cache server too on our local machines. At first install, Chocolatey https://chocolatey.org/ , to make installation of Redis easy. Also, the version under Chocolatey supports more commands and compatible with Official Cache package from Microsoft. After Chocolatey installation hit choco install redis-64 . Once the installation is done, we can start the server by running redis-server . Distributed Cache package and registration dotnet core provides IDistributedCache interface which can be overrided with our own implementation. That is one of the beauties of dotnet core, having DI implementation at heart of framework. There is already nuget package available to override IDistributedCache i...

Using LINQ to Entity efficiently with First/FirstOrDefault/Last/LastOrDefault/Single/SingleOrDefault

We generally use these extension methods First/FirstOrDefault/Last/LastOrDefault/Single/SingleOrDefault with predicates like ctx=> ctx.Model.FirstOrDefault(item => item.Id == 1 ) Or ctx=> ctx.Model.Where(item => item.Id == 1 ).FirstOrDefault() What is the problem with these? FirstOrDefault or similar methods immediately loads all data at once. So, let's say we have fifty columns on table then all those columns data would be retrieved from DB and saved into memory. This link gives a fair idea of different function behavior.  https://msdn.microsoft.com/en-us/library/bb882641.aspx .  So, even if we require only one value from selected field it retrieves all values. What is the solution? The solution is pretty simple. Whenever we need selected items better to do projection before calling FirstOrDefault or similar methods. Ex: Selecting single item ctx.Model.Where(itm => itm.Id == 1) .Select(itm => itm.Name).FirstO...

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) { ...

Visual Studio 2015 Code Analyzer and configuration with StyleCop

What is Diagnostic/Code Analyzer? To put it simply it is something similar to Resharper or Telerik JustCode. It analyzes codes while writing on code editor and suggest for improvements of codes through Squiggles, light icon and based on various severity. How it works? I had mentioned that it is similar to Resharper and Telerik JustCode but internal infrastructure is completely different. It is dependent on new compiler Roslyn . Roslyn has a clever compile technique, unlike older version which makes it faster and flexible for dynamic compilation without the need of the entire code base. The structure is basically divided into two categories Syntax Tree , and Semantic Model . The syntax tree is related to syntaxes only it does not require any reference check. It can be related to DOM elements structure in case of HTML.  Syntax Tree consists of very fine details as simple as WhiteSpace under the code. The Semantic Model is kind of references of Syntax Tree in which it ...

Storing and restoring Kendo Grid state from Database

There is no any built in way to store entire grid state into database and restore back again with all filters, groups, aggregates, page and page size. At first, I was trying to restore only filters by looking through DataSourceRequest. DataSourceRequest is kind of communication medium between client and server for the operation we do on grid. All the request comes via DataSourceRequest. In previous approach, I was trying to store IFileDescriptor interface which come with class FileDescriptor by looping through filters and serializing into string for saving into database but this IFileDescriptor can also contain CompositeFilterDescriptor which can be nested in nested object which are very tricky to handle. So, I had decompiled entire Kendo.MVC library and found out that all Kendo MVC controls are derived from “JsonObject”. It is there own implementation with ”Serialize” abstract function and “ToJson” function. In controls they are overriding “Serialize” method which depicts t...