Skip to main content

ASP.NET Core environment aware strongly typed configuration in MongoDB

This is targetted to save in MongoDB but the technique can be used in any targetted backend with key value setting based on IConfigurationProvider Data property.

Basically, the provided interface works based Data property having a type as IDictionary<string, string>. So, whatever class we create it has to be serialized based on same. We would simplify this by creating an abstract class to have certain serialization logic.

This is sample setting for the application. If you check the structure,  Setting is the main class and nested items are Azure, Message, Email, Twilio. The key value needs to be composed based on parent and child classes separated by colons.



Just like above, we need to populate settings from our different setting classes.

Implementation can be grouped in these sections.
- Application level configuration classes.
- Registration of configuration on ASP.NET Core.
- Environment level configuration, this would little mixed with above.

Application level configuration classes

Abstract class implementation for serialization and tracking name

 /// <summary>  
 /// To configuration data as per AspNet Core Configuration.  
 /// </summary>  
 public abstract class DataConfigurationObject  
 {  
   /// <summary>  
   /// Initializes a new instance of the <see cref="DataConfigurationObject"/> class.  
   /// </summary>  
   /// <param name="settingName">Name of the setting.</param>  
   public DataConfigurationObject(string settingName)  
   {  
     SettingName = settingName;  
   }  
   /// <summary>  
   /// Gets or sets the name of the parent setting name.  
   /// </summary>  
   /// <value>  
   /// The name of the parent setting name.  
   /// </value>  
   protected string SettingName { get; set; }  
   /// <summary>  
   /// Serializes the implementation for data.  
   /// </summary>  
   /// <param name="data">The application data.</param>  
   protected abstract void Serialize(IDictionary<string, string> data);  
   /// <summary>  
   /// Serialize data based on configuration.  
   /// </summary>  
   /// <returns>The configuration data.</returns>  
   public IDictionary<string, string> ToConfigData()  
   {  
     var value = new Dictionary<string, string>();  
     Serialize(value);  
     return value;  
   }  
 }

There are three key things to mark from above class:

SettingName  for root level setting name like Azure, Email etc from above-given example.

Serialize for seralization logic implementation on each configuration class.

ToConfigData for returning serialize data to consume on configuration classes.

Whatever configuration class we create it would be using same, for help in serialization.

There is one more item that each configuration class would be inheriting is to create default values for each configuration class. This could be implemented through an Interface to easy access.

Interface for the creation of default values for configuration.

 This would help to create default values for any class/configuration.

   /// <summary>  
   /// The default value generation for the class.  
   /// </summary>  
   /// <typeparam name="T"></typeparam>  
   public interface IDefault<T>  
     where T : class  
   {  
     /// <summary>  
     /// Creates the default for the class.  
     /// </summary>  
     /// <returns>Default value for the model.</returns>  
     T CreateDefault();  
   }



Implementation of root-level application configuration






 /// <summary>  
 /// Application settings.  
 /// </summary>  
 /// <seealso cref="DataConfigurationObject" />  
 public class Setting  
      : DataConfigurationObject, IDefault<Setting>  
 {  
      /// <summary>  
      /// Initializes a new instance of the <see cref="Setting"/> class.  
      /// </summary>  
      public Setting()  
           : base(nameof(Setting))  
      {  
           Azure = new AzureSetting();  
           Message = new MessageSetting();  
      }  
      /// <summary>  
      /// Gets or sets the name of the application.  
      /// </summary>  
      /// <value>  
      /// The name of the application.  
      /// </value>  
      public string AppName { get; set; }  
      /// <summary>  
      /// Gets or sets the Azure level application settings.  
      /// </summary>  
      /// <value>  
      /// The azure level application setting.  
      /// </value>  
      public AzureSetting Azure { get; set; }  
      /// <summary>  
      /// Gets or sets the message.  
      /// </summary>  
      /// <value>  
      /// The message.  
      /// </value>  
      public MessageSetting Message { get; set; }  
      /// <summary>  
      /// Creates the default for the class.  
      /// </summary>  
      /// <returns>  
      /// Default value for the model.  
      /// </returns>  
      public Setting CreateDefault()  
      {  
           return new Setting  
           {  
                AppName = "My Project - App",  
                Azure = Azure.CreateDefault(),  
                Message = Message.CreateDefault()  
           };  
      }  
      /// <summary>  
      /// Serializes the implementation for data.  
      /// </summary>  
      /// <param name="data">The application data.</param>  
      protected override void Serialize(IDictionary<string, string> data)  
      {  
           data.Add("Setting:AppName", AppName);  
           Azure.ToConfigData().ToList().ForEach(data.Add);  
           Message.ToConfigData().ToList().ForEach(data.Add);  
      }  
 }  




The key elements to mark from above.



- Constructor and base class constructor initialization did by providing the setting name on constructor by passing nameof(Setting) which means "Setting:" as a string. The Setting: string which is used to identify class from ASP.NET Core. It is used to set root level name for the configuration.

- AzureSetting, MessageSetting are nested classes which would have a similar implementation as this class.

- AppName is a property that would initialize in Serialize.

- CreateDefault is a function to set up default values for configuration.

- Serialize method uses two things. First to serialize property as data.Add("Setting:AppName", AppName). The second thing is to add configuration from other child classes.ToList is just used to simplify by consuming of ForEach function to append configurations.



Child class configuration implementation.




 /// <summary>  
 /// Azure settings for the application.  
 /// </summary>  
 /// <seealso cref="DataConfigurationObject" />  
 /// <seealso cref="IDefault{AzureSetting}" />  
 public class AzureSetting  
      : DataConfigurationObject, IDefault<AzureSetting>  
 {  
      /// <summary>  
      /// Initializes a new instance of the <see cref="AzureSetting"/> class.  
      /// </summary>  
      public AzureSetting()  
           : base($"{nameof(Setting)}:{nameof(Setting.Azure)}")  
      {  
           AzureStorageAccount = new AzureStorageSetting();  
           AzureAd = new AzureDirectorySetting();  
      }  
      /// <summary>  
      /// Gets or sets the azure ad.  
      /// </summary>  
      /// <value>  
      /// The azure ad.  
      /// </value>  
      public AzureDirectorySetting AzureAd { get; set; }  
      /// <summary>  
      /// Gets or sets the azure storage account.  
      /// </summary>  
      /// <value>  
      /// The azure storage account.  
      /// </value>  
      public AzureStorageSetting AzureStorageAccount { get; set; }  
      /// <summary>  
      /// Creates the default for the class.  
      /// </summary>  
      /// <returns>  
      /// Default value for the model.  
      /// </returns>  
      public AzureSetting CreateDefault()  
      {  
           return new AzureSetting  
           {  
                AzureAd = AzureAd.CreateDefault(),  
                AzureStorageAccount = AzureStorageAccount.CreateDefault()  
           };  
      }  
      /// <summary>  
      /// Serializes the implementation for data.  
      /// </summary>  
      /// <param name="data">The application data.</param>  
      protected override void Serialize(IDictionary<string, string> data)  
      {  
           AzureAd.ToConfigData().ToList().ForEach(data.Add);  
           AzureStorageAccount.ToConfigData().ToList().ForEach(data.Add);  
      }  
 }  




The only different over here is the initialization of base class through the constructor. Here full path is specified base($"{nameof(Setting)}:{nameof(Setting.Azure)}"). This is going to be the last example of nested configuration.






 /// <summary>  
 /// Azure storage account settings.  
 /// </summary>  
 public class AzureStorageSetting  
   : DataConfigurationObject, IDefault<AzureStorageSetting>  
 {  
   /// <summary>  
   /// Initializes a new instance of the <see cref="AzureStorageSetting"/> class.  
   /// </summary>  
   public AzureStorageSetting()  
     : base($"{nameof(Setting)}:{nameof(Setting.Azure)}:{nameof(AzureSetting.AzureStorageAccount)}")  
   {  
   }  
   /// <summary>  
   /// Gets or sets the access key.  
   /// </summary>  
   /// <value>  
   /// The access key.  
   /// </value>  
   public string AccessKey { get; set; }  
   /// <summary>  
   /// Gets or sets the name of the storage account.  
   /// </summary>  
   /// <value>  
   /// The name of the storage account.  
   /// </value>  
   public string StorageAccountName { get; set; }  
   /// <summary>  
   /// Creates the default for the class.  
   /// </summary>  
   /// <returns>  
   /// Default value for the model.  
   /// </returns>  
   public AzureStorageSetting CreateDefault()  
   {  
     return new AzureStorageSetting  
     {  
       AccessKey = "<AccessKeySetting>",  
       StorageAccountName = "<StorageAccountNameSetting>"  
     };  
   }  
   /// <summary>  
   /// Serializes the implementation for data.  
   /// </summary>  
   /// <param name="data">The application data.</param>  
   protected override void Serialize(IDictionary<string, string> data)  
   {  
     Func<string, string> nameValue = name => $"{SettingName}:{name}";  
     data[nameValue(nameof(StorageAccountName))] = StorageAccountName;  
     data[nameValue(nameof(AccessKey))] = AccessKey;  
   }  
 }  




Now you see the pattern, how it is being initialized on the constructor, default value, and property values.



In last part, we would be setting all configuration based on environments like Development, Staging, Production and so on...



Master root level setting to save based on different environments




 /// <summary>  
 /// Application settings for the application.  
 /// </summary>  
 public class AppSetting  
 {  
   /// <summary>  
   /// Gets or sets the Environment identifier.  
   /// </summary>  
   /// <value>  
   /// The Environment identifier.  
   /// </value>  
   [BsonId]  
   public string Id { get; set; }  
   /// <summary>  
   /// Gets or sets the value for application level settings.  
   /// </summary>  
   /// <value>  
   /// The application level settings.  
   /// </value>  
   public Setting Value { get; set; }  
 }  




The Id would save environment name Value would have application level settings.





Registration of configuration on ASP.NET Core

This would be divided into three parts ConfigurationProvider, IConfigurationSource and registration with IOption.



Let's start with the main item which would set up all the configuration classes we created.



Implementation of configuration provider




 using Microsoft.Extensions.Configuration;  
 using MongoDB.Driver;  
 /// <summary>  
 /// Configuration provider for NoSql  
 /// </summary>  
 /// <typeparam name="TSetting">The type of the setting.</typeparam>  
 /// <seealso cref="Microsoft.Extensions.Configuration.ConfigurationProvider" />  
 public class ConfigurationProviderNoSql<TSetting>  
   : ConfigurationProvider  
   where TSetting : DataConfigurationObject  
 {  
   /// <summary>  
   /// The environment type  
   /// </summary>  
   private readonly EnvironmentType EnvironmentType;  
   /// <summary>  
   /// The mongo database  
   /// </summary>  
   private readonly IMongoDatabase MongoDb;  
   /// <summary>  
   /// Initializes a new instance of the <see cref="ConfigurationProviderNoSql{TSetting}"/> class.  
   /// </summary>  
   /// <param name="mongoDatabase">The mongo database.</param>  
   /// <param name="environmentType">Type of the environment.</param>  
   public ConfigurationProviderNoSql(IMongoDatabase mongoDatabase, EnvironmentType environmentType)  
   {  
     MongoDb = mongoDatabase;  
     EnvironmentType = environmentType;  
   }  
   /// <summary>  
   /// Gets or sets the application setting.  
   /// </summary>  
   /// <value>  
   /// The application setting.  
   /// </value>  
   public Setting Setting { get; set; }  
   /// <summary>  
   /// Gets the application setting collection.  
   /// </summary>  
   /// <value>  
   /// The application setting collection.  
   /// </value>  
   protected IMongoCollection<AppSetting> AppSettingCollection =>  
     MongoDb.GetCollection<AppSetting>("SystemApplicationSetting");  
   /// <summary>  
   /// Loads this instance.  
   /// </summary>  
   public override void Load()  
   {  
     var value = AppSettingCollection.Find(item => item.Id == EnvironmentType.ToString()).FirstOrDefault();  
     if (value == null)  
     {  
       value = new AppSetting  
       {  
         Id = EnvironmentType.ToString(),  
         Value = new Setting().CreateDefault()  
       };  
       AppSettingCollection.InsertOne(value);  
     }  
     Setting = value.Value;  
     Data = value.Value.ToConfigData();  
   }  
 }  




The codes over here are pretty understandable and straight to just consume whatever we created through those previous configuration classes. It is using Load function and Data property from ConfigurationProvider class.



NOTE: I have used generic class but not fully implemented.



The EnvironmentType enum is just based on the environment we want to have. This is an example.




 /// <summary>  
 /// Environment type.  
 /// </summary>  
 public enum EnvironmentType  
 {  
   /// <summary>  
   /// The Development environment.  
   /// </summary>  
   Development,  
   /// <summary>  
   /// The Staging environment.  
   /// </summary>  
   Staging,  
   /// <summary>  
   /// The Production environment.  
   /// </summary>  
   Production,   
 }  




The IConfigurationSource implementation




 using Microsoft.Extensions.Configuration;
 using MongoDB.Driver; 
 /// <summary>  
 /// Configuration based on MongoDB.  
 /// </summary>  
 /// <typeparam name="TSetting">The type of the setting.</typeparam>  
 /// <seealso cref="Microsoft.Extensions.Configuration.IConfigurationSource" />  
 public class NoSqlConfigurationSource<TSetting>  
   : IConfigurationSource  
   where TSetting : DataConfigurationObject  
 {  
   /// <summary>  
   /// The mongo database  
   /// </summary>  
   private readonly IMongoDatabase MongoDb;  
   /// <summary>  
   /// The environment type  
   /// </summary>  
   private readonly EnvironmentType EnvironmentType;  
   /// <summary>  
   /// Initializes a new instance of the <see cref="NoSqlConfigurationSource{TSetting}"/> class.  
   /// </summary>  
   /// <param name="mongoDatabase">The mongo database.</param>  
   /// <param name="environmentType">Type of the environment.</param>  
   public NoSqlConfigurationSource(IMongoDatabase mongoDatabase, EnvironmentType environmentType)  
   {  
     MongoDb = mongoDatabase;  
     EnvironmentType = environmentType;  
   }  
   /// <summary>  
   /// Builds the <see cref="T:Microsoft.Extensions.Configuration.IConfigurationProvider" /> for this source.  
   /// </summary>  
   /// <param name="builder">The <see cref="T:Microsoft.Extensions.Configuration.IConfigurationBuilder" />.</param>  
   /// <returns>  
   /// An <see cref="T:Microsoft.Extensions.Configuration.IConfigurationProvider" />  
   /// </returns>  
   public IConfigurationProvider Build(IConfigurationBuilder builder)  
   {  
     return new ConfigurationProviderNoSql<TSetting>(MongoDb, EnvironmentType);  
   }  
 }  
 /// <summary>  
 /// Configuration based on MongoDB.  
 /// </summary>  
 /// <seealso cref="Microsoft.Extensions.Configuration.IConfigurationSource" />  
 public class NoSqlConfigurationSource  
 : NoSqlConfigurationSource<AppSetting>  
 {  
   /// <summary>  
   /// Initializes a new instance of the <see cref="NoSqlConfigurationSource"/> class.  
   /// </summary>  
   /// <param name="mongoDatabase">The mongo database.</param>  
   /// <param name="environmentType">Type of the environment.</param>  
   public NoSqlConfigurationSource(IMongoDatabase mongoDatabase, EnvironmentType environmentType)  
     : base(mongoDatabase, environmentType)  
   {  
   }  
 }  




It just initializes what we already created.



The extension method and usage for wiring up configuration.




 using Microsoft.Extensions.Configuration;  
 using MongoDB.Driver;  
 using System;  
 /// <summary>  
 /// MongoDB configuration helper.  
 /// </summary>  
 public static class MongoDbConfigExtension  
 {  
   /// <summary>  
   /// Adds the mongo database configuration.  
   /// </summary>  
   /// <param name="builder">The builder.</param>  
   /// <param name="environmentType">Type of the environment.</param>  
   /// <param name="option">The action for creation of Mongo database.</param>  
   /// <returns>Configuration builder after NoSql configuration.</returns>  
   public static IConfigurationBuilder AddMongoDbConfig(  
     this IConfigurationBuilder builder, EnvironmentType environmentType, Func<IMongoDatabase> option)  
   {  
     return builder.Add(new NoSqlConfigurationSource(option(), environmentType));  
   }  
 }  






Startup.cs settings.




 /// <summary>  
 /// Gets or sets the configuration.  
 /// </summary>  
 /// <value>The configuration.</value>  
 public IConfigurationRoot Configuration { get; set; }  
 /// <summary>  
 /// Gets or sets the application setting.  
 /// </summary>  
 /// <value>  
 /// The application setting.  
 /// </value>  
 public Setting Setting { get; set; }            
 /// <summary>  
 /// Initializes a new instance of the <see cref="Startup"/> class.  
 /// </summary>  
 /// <param name="env">The environment type.</param>  
 public Startup(IHostingEnvironment env)  
 {  
   var envType = (EnvironmentType)Enum.Parse(typeof(EnvironmentType), env.EnvironmentName);  
   // work with with a builder using multiple calls  
   var builder = new ConfigurationBuilder()  
     .SetBasePath(env.ContentRootPath)  
     .AddJsonFile("appsettings.json", optional: true, reloadOnChange: true);  
   var connectionStringConfig = builder.Build();  
   // chain calls together as a fluent API  
   var config = new ConfigurationBuilder().SetBasePath(env.ContentRootPath).AddMongoDbConfig(envType,  
       () => new MongoClient(connectionStringConfig  
         .GetConnectionString($"MongoDatabase{env.EnvironmentName}"))  
         .GetDatabase($"MyProject{env.EnvironmentName}"))  
     .AddJsonFile("appsettings.json", optional: true, reloadOnChange: true)  
     .AddJsonFile($"appsettings.{env.EnvironmentName}.json", optional: true, reloadOnChange: true)  
     .AddEnvironmentVariables();  
   Configuration = config.Build();  
   Environment = env;  
   Setting = Configuration.Get<Setting>(nameof(Setting));  
 }  
 public void ConfigureServices(IServiceCollection services)  
 {  
      // Configuration DI  
      services.AddSingleton<IConfigurationRoot>(Configuration);  
      services.AddSingleton<IConfiguration>(Configuration);  
      services.AddOptionModels(Configuration, (config) =>  
      {  
           config = Configuration.Get<Setting>(nameof(Setting));  
      });  
      services.AddSingleton((option) =>  
      {  
           return Configuration.Get<Setting>(nameof(Setting));  
      });       
 }  




The builder is to get the connection string from appSettings.json file and use that connection string to initialize configuration through AddMongoDbConfig extension method.



Now, the Setting DI should work on any constructor injection.



NOTE: Few DI were done for a testing purpose. You can use as per need.













Labels:

































Comments











Post a Comment



















Popular posts from this blog



















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




















1 comment









Read more




























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




















4 comments









Read more




























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




















1 comment









Read more




























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




















Post a Comment









Read more




























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




















1 comment









Read more




























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




















Post a Comment









Read more




























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();            thro...




















Post a Comment









Read more




























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




















Post a Comment









Read more




























A wrapper implementation for Kendo Grid usage




























 A wrapper implementation for any heavily used item is always a good practice. Whatever is not written by us and used at a lot of places should be wrapped within specific functionality to keep it future proof and easily changeable. This also encourages DRY principle to keep our common setting at a central place. Kendo UI items are enormous in configuration, one of an issue I find people keep repeating codes for Kendo Grid configuration. They have built very flexible system to have any configuration, but in most of the cases, we do not need all of those complicated configuration. We would try to see a simpler configuration of same. The actual core implementation is bit complex, but we do not have to bother about it once done since the focus is just on usage only. I recommend doing this practice for as simple as jQuery events, form handling or as simple as any notification system. This just won't make things simple but makes codes much more manageable, easy understand, read or open f...




















Post a Comment









Read more






























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




















3 comments









Read more