|
It has been a long time since Entity Framework 6 has been released. Any ideas on when we will finally get a working EF6 Provider? Having to wait for such a trivial thing like porting a working EF5 provider to EF6.* for over half a year is really disappointing. |
|
UPDATE: There was an additional problem with the EF6 design-first wizard found during further testing. This has now been fixed in 12.0.1.4162 and 16.0.0.2014, see CR #770760. Code-first projects should still work with the current support. Windows x86/x64 Support Packages (12.0.1 SP 80 and above, 16.0 SP 19 and above) have been released with this update. How to build an Entity Framework 6 Project with SQL Anywhere 12.0.1.4162 and 16.0.0.2014 and aboveIn order to build an Entity Framework 6 project with SQL Anywhere:
For me "/v 6" didn't work. I had to use "/v EF6". I'm using SA 16.0.0.2158.
(21 Mar '16, 19:04)
rlenders
|
|
FWIW, Windows 12.0.1 and 16.0 EBFs containing the EF6 provider seem to be available for some weeks: - cf. this CR note.
Note: I do not use EF, so I can't tell whether they work as expected, I just noticed the section in the EBF Readme... ================(Build #4142 - Engineering Case #768717)================
The ADO.NET provider now supports Entity Framework 6. A new dll (iAnywhere.Data.SQLAnywhere.EF6.dll)
has been added to %SQLANY%\Assembly\V4.5 directory. SetupVSPackage still
registers the v4.5 dll. To use the new Entity Framework 6 provider, register
it in app.config or web.config.
...
1
Thanks Volker for highlighting this support. Yes, we do officially now support Entity Framework 6.0.x now with the above CRs and builds. However, there is one known issue with this support. When using the Model-first designer in EFTools 6.0, it is possible to encounter the following message:
This is a known bug in EF6: "EF Designer cannot load 3rd party provider if a project has not been built" https://entityframework.codeplex.com/workitem/1869 Building the project for the first time while the EF6 assemblies are present and referenced will resolve the issue, as mentioned in the article above.
(16 Sep '14, 16:25)
Jeff Albion
Replies hidden
FYI: This particular issue has been resolved in EFTools 6.1.2 and higher. See: https://entityframework.codeplex.com/SourceControl/changeset/c76104ccffbff12f182b3280b992eba196c3625b Now having a clean build should no longer result in the inability to find the provider and the build step listed in my other answer is not required.
(23 Jan '15, 10:33)
Jeff Albion
|
|
I performed all the steps in the above message and STILL had the problem. I finally stumbled on the following fix on another forum (stackoverflow) and wanted to add the fix to this posting in the hope I save some poor soul the the lost time I experienced. Note: This fix is for version 17. The fix for 12 or 16 would be the same with appropriate references changed. You must replace the entity framework section in app.config (web.config) with the following (remove blank lines)... <system.data> <DbProviderFactories> <clear /> <add name="SQL Anywhere 17 Data Provider" invariant="Sap.Data.SQLAnywhere" description=".Net Framework Data Provider for SQL Anywhere 17" type="Sap.Data.SQLAnywhere.SAFactory, Sap.Data.SQLAnywhere.EF6, Version=17.0.0.10094, Culture=neutral, PublicKeyToken=f222fc4333e0d400" /> </DbProviderFactories> </system.data> <entityframework> <defaultConnectionFactory type="Sap.Data.SQLAnywhere.SAConnectionFactory, Sap.Data.SQLAnywhere.EF6, Version=17.0.0.10094, Culture=neutral, PublicKeyToken=f222fc4333e0d400"> </defaultConnectionFactory> <providers> <provider invariantName="Sap.Data.SQLAnywhere" type="Sap.Data.SQLAnywhere.SAProviderServices, Sap.Data.SQLAnywhere.EF6, Version=17.0.0.10094, Culture=neutral, PublicKeyToken=f222fc4333e0d400" /> </providers> </entityframework> |
We are currently working on EF6 support for SQLA. Don't have a timeframe yet, but hopefully soon. For the benefit of others, I'll reply to this thread when our EF6 support is available.
Come on guys. It has been 10 Month now since EF6 was released. If you don’t want to support EF6.* just say it.
“Planning” to support it for over 10 Month is ridiculous, especially when you see other companies updating their provider within weeks.
We are very close to completing our support for EF6. Once this is done, I will post a message in the forum indicating its availability. Thanks for your patience.
The SAP developer site provides a download for EBF 4134 ... How can we get our hands on EBF 4142?
Hello sbhyde,
For information about how to obtain current Support Packages for SQL Anywhere, see my answer here. If you don't have an older Sybase support agreement to access the older Sybase EBF site, you will need to have a current SAP support agreement in order to obtain access.