For up to date information on upgrading to Entity Framework 6, visit the Upgrading to EF6 page on our MSDN site.


 

 

 

Last edited Dec 18, 2013 at 4:29 PM by RoMiller, version 9

Comments

dirq Sep 3, 2013 at 2:24 PM 
Also, remember to change the using statements in your t4 templates like your Context.tt file so regenerations continue to work.

using System.Data.Objects; --> using System.Data.Entity.Core.Objects;
using System.Data.Objects.DataClasses; --> using System.Data.Entity.Core.Objects.DataClasses;

tilovell Jul 18, 2013 at 7:22 PM 
Right now I am caring about a DynamicData project. (Small world of hurt. :( )
Additional guidance on that would be good.

alexdresko Apr 3, 2013 at 6:22 PM 
Not that anyone cares, I don't believe, but moving ObjectContext breaks DynamicData projects that use DbContext as well.

ajcvickers Mar 18, 2013 at 4:19 PM 
@NelsonReis Thanks for pointing that out. I removed it from this list, as well as the comment about partial trust, which is also now supported.

NelsonReis Mar 18, 2013 at 12:43 PM 
Is the below limitation still valid, as of EF6 Alpha3, or is .NET4 already supported?
"EF6 currently only supports .NET 4.5 and your application must target .NET 4.5. to use EF6. As work progresses we hope to update EF6 to support .NET 4."

johncrim Feb 22, 2013 at 7:13 AM 
One of the problems with changing the namespaces is that it breaks WCF data services (server component). WCF data services requires ObjectContext to be System.Data.Objects.ObjectContext .

moozzyk Dec 19, 2012 at 7:45 PM 
I think the name has changed to System.Data.Entity.DbFunctions. Types from System.Data.Entity.dll don't work with types from EntityFramework.dll (6.0.0.0) and vice versa so you may run into weird issues (the most "popular" one is treating EF5 geospatial types as Entity Types what causes an exception because a key property cannot be found)

fedefrank Dec 19, 2012 at 6:30 PM 
Hi
I Can't find System.Data.Entity.EntityFunctions on EntityFramework 6.0.0-alpha2 assembly. For the moment a reference both assemblies (System.Data.Entity.dll).
Could this cause any problems?
Thanks!!!