R – how to use Repository pattern to make it easy switch between ORMs

design-patternsgenericsnetrepository-pattern

I knew than one of the benefits from using repository pattern make it easy to switch between ORM, for example will implement data access code using Linq to sql and also using Ado.net entity framework, then using Dependency injection switch which one to use.

I saw KIGG doing the same "but its class diagram is complicated a little, at least for me as a beginner in repository pattern"

But i can't find an example describing this issue in details, i saw this example on codeproject its talking about generic repository implementation using Linq to sql, but can't use to switch to use another ORM.

where i can understand this issue? do you recommended an article or have your description?

Best Answer

I think that your repository implimentation will always be tied to whatever ORM or data access method it uses. Where the loose coupling is, is between the business logic (the repository interfaces) and the repository implimentations. You can create a new set of implimentations that meet the interface requirements, but impliment a different data access method. Once that's done it can be as easy as reconfiguring your IoC container to switch between the two...

Related Solutions

C# – How to use reflection to call a generic method

You need to use reflection to get the method to start with, then "construct" it by supplying type arguments with MakeGenericMethod:

MethodInfo method = typeof(Sample).GetMethod(nameof(Sample.GenericMethod));
MethodInfo generic = method.MakeGenericMethod(myType);
generic.Invoke(this, null);

For a static method, pass null as the first argument to Invoke. That's nothing to do with generic methods - it's just normal reflection.

As noted, a lot of this is simpler as of C# 4 using dynamic - if you can use type inference, of course. It doesn't help in cases where type inference isn't available, such as the exact example in the question.

Difference between static class and singleton pattern

What makes you say that either a singleton or a static method isn't thread-safe? Usually both should be implemented to be thread-safe.

The big difference between a singleton and a bunch of static methods is that singletons can implement interfaces (or derive from useful base classes, although that's less common, in my experience), so you can pass around the singleton as if it were "just another" implementation.

Best Answer

Related Solutions

C# – How to use reflection to call a generic method

Difference between static class and singleton pattern

Related Topic