Even though this is not a main line scenario it's not difficult to end up having a project that uses both System.Data.Entity.dll and EF6. A few scenarios are:
- I have a bigger app and would like to move to EF6 but want to do this gradually
- I have a bigger app that uses System.Data.Entity.dll and want to add new code that would use EF6
- I have an EF6 app and add an existing item to the project that happens to be an EF5 edmx file
I talked to Brice and this should actually work now since we register/unregister providers each time we need to talk to the database - so we just need some kind of exploratory testing to verify this is the case and we don't have weird errors/popups/asserts.
- I have a bigger app and would like to move to EF6 but want to do this gradually
- I have a bigger app that uses System.Data.Entity.dll and want to add new code that would use EF6
- I have an EF6 app and add an existing item to the project that happens to be an EF5 edmx file
I talked to Brice and this should actually work now since we register/unregister providers each time we need to talk to the database - so we just need some kind of exploratory testing to verify this is the case and we don't have weird errors/popups/asserts.
