This question is locked. New answers and comments are not allowed.
We decided to give Telerik Open Access a try mostly due to potential ability to perform schema migrations from designer (model first).
A couple of issues:
1. EF6 seems not to allow code generation templates other than T4 (no "default" option) http://stackoverflow.com/questions/19380820/change-ef-6-code-generation-strategy-from-t4 . This seems to be a requirement for the wizard to work.
2. During the attempted conversion we get an error: "The provider did not return a ProviderManifest instance".
MS VS2013 update 1, EF 6.02, Model First. App.config has correct connection string to local SQLEXPRESS database.
A couple of issues:
1. EF6 seems not to allow code generation templates other than T4 (no "default" option) http://stackoverflow.com/questions/19380820/change-ef-6-code-generation-strategy-from-t4 . This seems to be a requirement for the wizard to work.
2. During the attempted conversion we get an error: "The provider did not return a ProviderManifest instance".
MS VS2013 update 1, EF 6.02, Model First. App.config has correct connection string to local SQLEXPRESS database.
1 Answer, 1 is accepted
0
Hi Mikhail,
It is possible to use the conversion wizard in such scenario. While generally only the default code generation strategy is supported, it should not be an issue with conversion of Entity Framework 6 models.
As for the second issue that you are experiencing, it is a known problem. You could read more here. Fortunately, there is a workaround - you could open the .edmx as plain text, locate the ProviderManifestToken tag attribute and replace its value with 2008. Once this is done, rerun the Entity Framework Conversion Wizard.
Do not hesitate to get back to us if you have any further question or you need any further assistance.
Regards,
Boyan
Telerik
It is possible to use the conversion wizard in such scenario. While generally only the default code generation strategy is supported, it should not be an issue with conversion of Entity Framework 6 models.
As for the second issue that you are experiencing, it is a known problem. You could read more here. Fortunately, there is a workaround - you could open the .edmx as plain text, locate the ProviderManifestToken tag attribute and replace its value with 2008. Once this is done, rerun the Entity Framework Conversion Wizard.
Do not hesitate to get back to us if you have any further question or you need any further assistance.
Regards,
Boyan
Telerik
OpenAccess ORM is now Telerik Data Access. For more information on the new names, please, check out the Telerik Product Map.