cancel
Showing results for 
Search instead for 
Did you mean: 

Entity Framework v6 support

Former Member
4,143

Entity Framework v6 is now released:

After upgrading from v4 to v6 I get the following error: System.InvalidOperationException: The 'Instance' member of the Entity Framework provider type 'iAnywhere.Data.SQLAnywhere.SAProviderServices, iAnywhere.Data.SQLAnywhere.v4.0, Version=12.0.1.38174, Culture=neutral, PublicKeyToken=f222fc4333e0d400' did not return an object that inherits from 'System.Data.Entity.Core.Common.DbProviderServices'. Entity Framework providers must inherit from this class and the 'Instance' member must return the singleton instance of the provider. This may be because the provider does not support Entity Framework 6 or later; see http://go.microsoft.com/fwlink/?LinkId=260882 for more information.

Is it so, that SQL Anywhere does not support Entity Framework v6?

Entity EF 6 support? Is there any timeframe for when EF 6 will be supported on v16 or latest EBF of v12?

Accepted Solutions (0)

Answers (1)

Answers (1)

MCMartin
Participant

SQLA 12.0.1.3817 is definitely too old. Anyway I don't think, that support for EF6 has already been added to the latest EBF of SQLA 12.0.1.
EF 5 should currently be supported.

VolkerBarth
Contributor
0 Kudos

FWIW, EF 5 is supported starting with 12.0.1.3817:

================(Build #3817  - Engineering Case #724639)================

A new library (iAnywhere.Data.SQLAnywhere.v4.5.dll) has been added for supporting 
    .NET 4.5 and Entity Framework 5. Now 4 versions of SA ADO.NET provider are 
    shipped:
    1 - iAnywhere.Data.SQLAnywhere.dll / policy.1x.0. iAnywhere.Data.SQLAnywhere.dll 
    – for .NET 2
    2 - iAnywhere.Data.SQLAnywhere.v3.5.dll / policy.1x.0. iAnywhere.Data.SQLAnywhere.v3.5.dll 
    – for .NET 3.x and 2
    3 - iAnywhere.Data.SQLAnywhere.v4.0.dll / policy.1x.0. iAnywhere.Data.SQLAnywhere.v4.0.dll 
    – for .NET 4
    4 - iAnywhere.Data.SQLAnywhere.v4.5.dll / policy.1x.0. iAnywhere.Data.SQLAnywhere.v4.5.dll 
    – for .NET 4.5

Note: I do not claim it would not be useful to switch to a (much) newer EBF like 12.0.1.3994, because that EBF lists a bunch of fixes in the category "SQL Anywhere - ADO.Net Managed Provider" ...