Skip to main content

MongoDB navigation property or making it behave as ORM in .Net

This is an implementation to make models to have  navigation properties work like ORM does for us.

What actually happens in ORM to make navigation properties work?
Entity Framework has proxy classes implementation to allow lazy loading and eager loading implementation. While creating proxy classes it also changes definitions for actual classes to make navigation properties work to get values based on Model's for navigation properties. Most of ORMs work in same fashion like Telerik DataAccess has enhancer tool which changes class definition at compile time to enable navigation properties.

In this implementation, we would retain the original class but we would have extension methods to allow initializing properties to have navigation proprieties work.


Let's first create desire model on which we need to implement. I am picking up simple one-to-many relationship example from Person to Address.


 public class Person  
 {  
   public int PersonId { get; set; }  
   public string Name { get; set; }  
   public ICollection<Address> Addresses { get; set; }  
 }  

 public class Address  
 {  
   public int AddressId { get; set; }  
   public int PersonId { get; set; }  
   public string Street { get; set; }  
   public Person Person { get; set; }  
 }  

Over here we have navigation property on Addresses from Person and Person from Address based on PersonId and AddressId.

This is not recommended way to do in case of NoSql implementation but in case, if arises. I am also putting Id's as primary key which is not the native case with NoSql.

This is a mapping implementation of Person model, which would initialize Addresses property to automatically fill.

 public static class PersonMapping  
 {  
   public static Person InitNavigation(this Person model, IMongoDatabase mongoDB)  
   {  
     var relatedInfo = mongoDB.GetCollection<Address>("Address");  
     model.Addresses = relatedInfo.Find(add => add.PersonId == model.PersonId).ToList();  
     return model;  
   }  
 }  

The implementation is done with the ToList projection which would fill data into memory on InitNavigation function call only.

The usage can be very simple now.
 var mongoDb = new MongoClient("<connection string>").GetDatabase("<database>");  
 var personData = mongoDb.GetCollection<Person>(nameof(Person)).Find(per => per.PersonId == 1)  
   .FirstOrDefault().InitNavigation(mongoDb);  
 var person1addresses = personData.Addresses;  

We just need to compose the query and get a single item, once that is retrieved we can have a call to InitNavigation to initialise navigation property.

This is just a concept of implementation which can be extended based on need like instead of generating mapping manually T4 can be used to generate those codes automatically.

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 ASPNet Core Identity in MVC Core

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.

AspNet Identity Core is a new offering from Microsoft in replacement of AspNet Identity for managing users.

In this tutorial, we would be looking for implementing LDAP with AspNet Identity Core to allow users to be able to log in through AD or AspNet Identity Core members.

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 functiona…

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