Entity Framework 6.* provider

[Former Member]

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.

[Former Member]

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.

[Former Member]

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.

[Former Member]

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.

[Former Member]

The SAP developer site provides a download for EBF 4134 ... How can we get our hands on EBF 4142?

[jeff_albion]

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.

[VolkerBarth]

FWIW, Windows 12.0.1 and 16.0 EBFs containing the EF6 provider seem to be available for some weeks: - cf. this CR note.

• 12.0.1.4142 has been published on 2014-08-13

• 12.0.1.4155 has been published on 2014-09-06

• 16.0.0.2003 has been published on 2014-09-05

---

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.
...

[jeff_albion]

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.

[jeff_albion]

FYI: This particular issue has been resolved in EFTools 6.1.2 and higher. See: https://entityframework.codeplex.com/SourceControl/changeset/c76104ccffbff12f182b3280b992eba196c3625...

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.