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

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

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

Getting started with Raspberry Pi

Raspberry Pi is a small, low powered motherboard contains 512 RAM, combined CPU and GPU. It has LAN, 2 USB, HDMI input, Audio Out, SD Card reader and S-Video connectors. We can have many Linux distribution OS on it. To configure, we just need to attach SD Card to it. SD Card could range from class 4 to class 10. In some cases Raspberry Pi could support less then class 4 cards too. It could be powered through mini USB mobile charger. Let's get started with installing OS on SD Card. There are various ways to install OS. Like we can download OSes through  http://www.raspberrypi.org/downloads  and follow the instructions given on it. There is something BerryBoot multi-boot loader through which we can have more then one OS on Raspberry Pi and boot OS according to our need.  http://www.berryterminal.com/doku.php/berryboot  instructions could be followed to install OS with very simple steps. You need to have internet connection on Raspberry Pi to install OS. It coul...

OpenId Authentication with AspNet Identity Core

This is a very simple trick to make AspNet Identity work with OpenId Authentication. More of all both approach is completely separate to each other, there is no any connecting point. I am using  Microsoft.AspNetCore.Authentication.OpenIdConnect  package to configure but it should work with any other. Configuring under Startup.cs with IAppBuilder app.UseCookieAuthentication(new CookieAuthenticationOptions { AuthenticationScheme = CookieAuthenticationDefaults.AuthenticationScheme, LoginPath = new PathString("/Account/Login"), CookieName = "MyProjectName", }) .UseIdentity() .UseOpenIdConnectAuthentication(new OpenIdConnectOptions { ClientId = "<AzureAdClientId>", Authority = String.Format("https://login.microsoftonline.com/{0}", "<AzureAdTenant>"), ResponseType = OpenIdConnectResponseType.IdToken, PostLogoutRedirectUri = "<my website url>", ...

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

C# Response files

Response files are similar to batch files, having some specific instruction. On execution they perform some predefined task based on instruction. Response file contains instruction to compile programs. If we have to build complex program through command line then response files are really helpful in development process. rsp is an extension for response files. By default, csc.rsp file exists under "Framework" folder Ex: C:\Windows\Microsoft.NET\Framework\v4.0.30319. csc.rsp contains long list of system references (dlls). Some contents under csc.rsp # Reference the common Framework libraries /r:Accessibility.dll /r:Microsoft.CSharp.dll /r:System.Configuration.dll /r:System.Configuration.Install.dll /r:System.Core.dll /r:System.Data.dll /r:System.Data.DataSetExtensions.dll /r:System.Data.Linq.dll .......... In same way we can have our own response file defined which might include some third party dll. Let's see an example. Suppose we have to create an appli...

Implementing/Automating audit logs in Telerik Data Access

Audit logs can be tedious task if done manually, also developer might miss to update audit log implementation on certain level. The codes would be repeated on all places if not centralized. There are many approach available to maintain change history of model/table. Like having single history table and manage all changes of all models in same table. We may maintain in same table with some flags and JSON data for change list. We will look for maintaining history table based on each required data models with minimum effort and performance. To reduce code, I am going to use T4 to generate history models automatically based on original model. Also we are going to take care of Artificial type values. Step 1 - Create a custom attribute to mark model that history need to be maintained. /// <summary> /// Attribute to maintain history table /// </summary> [AttributeUsage(AttributeTargets.Class)] public class ManageHistoryAttribute : Attribute ...