Skip to main content

Entity Framework: How to get in a generic way entities from EF based on entity IDs

Offtopic:
I’m back. After a few weeks when I was blocked with personal projects, I’m back on the field, ready to write technical content.
Today I’ll start with something lights that can make our day more beautiful.

How we can write a generic method to get an entity from database using Entity Framework?
Let’s assume that we have different types of entities and we would like to obtain a specific entity using a generic method. Each entity can have the primary key field called in different ways. Also the type of the field can be different (one can be string, another one int and so on).
For this cases we should use Find method. This method accept as input parameters a collections of objects that represents the keys of the entity. Using this method we can get entities from EF in a generic way.
For compound keys, you need to specify the keys in the same order you specified them when you mapped the entity in EF.
Why a list of keys and not only one input parameter?
Well, we can have entities that has a compound key (a key formed from more than one field). For this cases we need to be able to specify the list of keys.
How to get a DbSet based on entity type?
When we need to get a specific DbSet based on the entity type we can use the Set method of DbContext. This methods returns the DbSet for specific entity.

Code sample:
FooDbContext fooContext = new FooDbContext();
// Get DbSet from DbContext
DbSet<Foo> fooSet = fooContext.Set<Foo>();

// Foo with id=2
Foo foo = fooSet.Find(2);

// Get entity with a compound key where key is ("BMW","M3")
DbSet<Car> carSet = fooContext.Set<Car>();
Car bmwM3 = carSet.Find("BMW",M3");

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…