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.

asked 16 Jun '14, 05:09

codeworx's gravatar image

codeworx
45123
accept rate: 0%

1

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.

(16 Jun '14, 10:48) José Ramos

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.

(06 Aug '14, 04:59) codeworx
1

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.

(07 Aug '14, 14:27) José Ramos

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

(16 Sep '14, 17:42) sbhyde
Replies hidden
Comment Text Removed
Comment Text Removed

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.

(20 Sep '14, 11:19) Jeff Albion

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 above

In order to build an Entity Framework 6 project with SQL Anywhere:

  • Install the Entity Framework 6 Tools for Visual Studio 2012 & 2013
  • Run SetupVSPackage.exe with the newly added “/v 6” option to register the Entity Framework 6 Provider (in machine.config). (Note: This replaces the current 'iAnywhere.Data.SQLAnywhere' invariant to use an EF6-compatible provider)
  • Install Entity Framework NuGet Package for the Visual Studio project. In the package manager console, type:

Install-Package EntityFramework

  • Modify the project app.config file to include the SQL Anywhere Entity Framework 6 provider. Here’s an example:

    <providers> <provider invariantname="iAnywhere.Data.SQLAnywhere" type="iAnywhere.Data.SQLAnywhere.SAProviderServices, iAnywhere.Data.SQLAnywhere.EF6, Version=16.0.0.20144, Culture=neutral, PublicKeyToken=f222fc4333e0d400"/> </providers>

  • Build the Visual Studio project.

  • Run Entity Data Model Wizard (Add -> New Item -> ADO.NET Entity Data Model).
permanent link

answered 19 Sep '14, 15:07

Jeff%20Albion's gravatar image

Jeff Albion
10.7k171174
accept rate: 24%

edited 14 Apr '15, 10:19

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.

  • 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.
...
permanent link

answered 09 Sep '14, 05:38

Volker%20Barth's gravatar image

Volker Barth
30.3k300452659
accept rate: 32%

edited 09 Sep '14, 05:43

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:

alt text

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
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×65

question asked: 16 Jun '14, 05:09

question was seen: 5,077 times

last updated: 21 Mar '16, 19:04