Updating pointers visual studio
Moving from EF4 directly to EF6 has a few extra challenges, plus my old solution used a T4 template that doesn’t have a direct replacement. Though I’m focusing on a bigger leap—from EF4 to EF6—you need to follow the same path of namespace fixes if you’re going from EF5 to EF6, because these namespace changes occurred between EF5 and EF6.In this case, my suggested course was to first update the EF version without making any other changes, and then make sure everything continued to work. Data in this way were moved to the new namespace root, System. After a series of iterative namespace fixes and rebuilds, which took only a few minutes for this small solution, I was able to successfully build and run the application—viewing, editing and saving data. My solution used an EDMX—an Entity Data Model designed and maintained with the EF Designer.The next step involved identifying an area of the model that could be extracted into a new small model. Because I created it in Visual Studio 2010 with EF4, it relied on an older code-generation template that generated an Object Context to manage all of the data persistence and caching. NET Framework and all of its DLLs lived in the Windows Global Assembly Cache (GAC). If you’re used to getting Entity Framework using the Nu Get Package distribution, you’ll need to think back to a time when EF was simply part of the .
To see what else is new in EF6, check out my December 2013 article, “Entity Framework 6: The Ninja Edition” (bit.ly/1q Jgwlf).
When updating existing applications to EF6, I just let the compiler highlight the changes by showing me any “The type or namespace …
While the application is now using the most recent version of Entity Framework, it’s benefitting only from the underlying improvements to Entity Framework—in particular some great performance gains that came in EF5 and EF6.
Many of the improvements are related features of the Db Context API and Code First.
If you want to update to EF6 and also update to Db Context, I recommend starting with the simple upgrade to EF6, and getting everything working again before you begin to shift to the Db Context API.