Be careful when you upgrade to Entity Framework 6, because it introduces some breaking changes.
Entity Framework 6 is the first version that is not tied to the .NET framework directly. This allows Entity Framework to evolve independently from the .NET framework. Unfortunaltey this couldn’t be done without introducing some breaking changes.
From the MSDN site:
Types like ObjectContext that were previously in System.Data.Entity.dll have been moved to new namespaces. This means you may need to update your using or Import directives to build against EF6.
The general rule for namespace changes is that any type in System.Data.* is moved to System.Data.Entity.Core.*. In other words, just insert Entity.Core. after System.Data. For example:
- System.Data.EntityException => System.Data.Entity.Core.EntityException
- System.Data.Objects.ObjectContext => System.Data.Entity.Core.Objects.ObjectContext
- System.Data.Objects.DataClasses.RelationshipManager => System.Data.Entity.Core.Objects.DataClasses.RelationshipManager
These types are in the Core namespaces because they are not used directly for most DbContext-based applications. Some types that were part of System.Data.Entity.dll are still used commonly and directly for DbContext-based applications and so have not been moved into the Core namespaces. These are:
- System.Data.EntityState => System.Data.Entity.EntityState
- System.Data.Objects.DataClasses.EdmFunctionAttribute =>System.Data.Entity.DbFunctionAttribute
Note: This class has been renamed; a class with the old name still exists and works, but it now marked as obsolete.
- System.Data.Objects.EntityFunctions => System.Data.Entity.DbFunctions
Note: This class has been renamed; a class with the old name still exists and works, but it now marked as obsolete.)
- Spatial classes (e.g. DbGeography, DbGeometry) have moved from System.Data.Spatial => System.Data.Entity.Spatial