Support for ASP.NET EntityDataSource and DynamicData for EF6
Because in EF6 the ObjectContext class is being moved into the EntityFramework assembly, existing code will treat it separately from the "old" ObjectContext in the System.Data.Entity assembly.
I use EF CodeFirst in a mixed MVC / WebForms(DynamicData) application.
Either bring out new versions of EntityDataSource and DynamicData for EF6 or provide a way from going from a EF4/5 ObjectContext to an EF6 one.
How are we supposed to easily upgrade / migrate existing projects that use EntityDataSource (sparingly or not), if you simply pull support for the control out of the product. Please provide an EntityDataSource control for those of us who like it's ease and use it in existing projects.
This was released. See the announcement here: http://blogs.msdn.com/b/webdev/archive/2014/02/28/announcing-the-release-of-dynamic-data-provider-and-entitydatasource-control-for-entity-framework-6.aspx
Flagship products like Visual Studio and EntityFramework should always work together. It's fine that the owners of EF changed the namespaces but I'm disappointed that they didn't bother to check each Visual Studio project type to make sure they didn't break it. Or they didn't bother to write an easy to find MSDN article that would save me hours of hopeless tinkering.
Eric J commented
DynamicData may not be mainstream, but no reason to dump it just because it may be used not much
Raphael L commented
Agree with all the comments below. If Microsoft can't provide an EntityDataSource, then they should provide some alternative for easy WebForms binding (an "old" technology still used in SharePoint 2013, for instance).
Jon Miller commented
I need EntityDataSource because it has support for filtering and paging in the SQL Server. I am using Telerik's RadGrid and need it for that. The data sets I'm working with are large. So, I need the filtering to happen in the database.
There are going to be a lot of broken Webforms sites if people upgrade to EF6 without checking first.
David Egli commented
David Egli commented
I would think that folks would expect to use the EntityDataSource with the Entity Framework no matter which version is running.