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.
Comments: Another interesting scenario is around validation where we have EF5 and EF6 models in the same project and the EF5 model is using non SqlServer/SqlServer CE provider. Would validation work for this model? (my worry is that the provider for the other one will not be registered and therefore it would fail). You may try closing and re-opening VS to clear the dependency resolver.
- 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.
Comments: Another interesting scenario is around validation where we have EF5 and EF6 models in the same project and the EF5 model is using non SqlServer/SqlServer CE provider. Would validation work for this model? (my worry is that the provider for the other one will not be registered and therefore it would fail). You may try closing and re-opening VS to clear the dependency resolver.