Support ADO.Net providers that contain EF implementations
ADO.Net is a provider model (factories). You can load and query the provider to see if it supports EF. That is the whole point of having ADO.Net as a provider. Adding each provider one at a time means a lot of hand coding per provider. It would seem to be a better use of your time to just support ADO.Net and the provider model.
This would allow you to use VistaDB, Sqlite, Oracle, MySql, etc as long as they have an EF provider that supports the provider factory correctly.
Jason Short
shared this idea
You can specify any provider and connection string from V2. Please note that this only works with static DataContexts – i.e., EDMs that you’ve defined yourself in VS. It’s not possible to do otherwise AFAIK there’s no general and reliable way to query schema via EF and ADO.NET.