Skip to main content

Enum generation for lookup table through T4

Sometime there is need of mapping some values from database to code level, basically in look up tables.
I am going to generate enum based on database values. In this example, I am going for T4 template to generate up enum by using SqlDataReader.
We can have any SQL query to generate enum. In my case, Privilege code, name and description from table would generate up enum.

 <#@ template debug="true" hostSpecific="true" #>  
 <#@ output extension=".cs" #>  
 <#@ Assembly Name="System.Data" #>  
 <#@ include file="EF.Utility.CS.ttinclude"#>  
 <#@ import namespace="System.Data.SqlClient" #>   
      var code = new CodeGenerationTools(this);  
      var connectString = "Set connection string";  
      var queryString = "select PrivilegeCode, PrivilegeName, PrivilegeDescription from Privilege";  
 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>  
   /// Different permission rules for users  
   /// </summary>  
      public enum PermissionRule  
 using (SqlConnection connection =  
       new SqlConnection(connectString))  
   SqlCommand command =  
     new SqlCommand(queryString, connection);  
   SqlDataReader reader = command.ExecuteReader();  
   // Call Read before accessing data.   
   while (reader.Read())  
     /// <summary>  
     /// <#=reader[1] #>  
     /// </summary>  
           /// <remarks><#=reader[2] #></remarks>  
           <#=reader[0] #>,  

Set connectString variable as desired database connection.
Set queryString to table that you want to connect.

Using those three columns I am able to generate enum having name, comment and remark. Now, if lookup table changes then I just need to do “Run Custom Tool” on template which would generate up new enum values without copying/pasting values on code level.

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": "", "System.DirectoryServices.AccountManagement": "" } } },
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.

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; }…