Cannot use Sql Anywhere 12 in entity framework

[Former Member]

Hello!

I use visual studio 2013, i executed setupvspackage.exe /i in both the v2.0 and v4.0 assemblies folder. I still cannot see SQL Anywhere 12 in the available data source list in the entity data model wizard. Please help!

Thanks!

[Former Member]

I have the same issue. I also executed setupvspackage.exe /i in both the v2.0 and v4.0 assemblies folder. The only option when picking Other is ".Net Framework Data Provider for SQL Server"

[jeff_albion]

This question is similar to this other question, recently answered:

---

The way Visual Studio displays the providers is based on the DbProviderFactories information pulled out of the machine.config file for your respective framework (e.g. C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319\\Config\\machine.config for .NET 4.0, x64). This looks at the registered <system.data> / <DbProviderFactories> section for available providers:

<system.data>
    <DbProviderFactories>
        <add name="SQL Anywhere 11 Data Provider" invariant="iAnywhere.Data.SQLAnywhere"
             description=".Net Framework Data Provider for SQL Anywhere 11" 
             type="iAnywhere.Data.SQLAnywhere.SAFactory, iAnywhere.Data.SQLAnywhere.v4.0, 
               Version=11.0.1.30694, Culture=neutral, PublicKeyToken=f222fc4333e0d400" />

If you're not seeing the SQL Anywhere .NET Provider in your Visual Studio dialog with the framework and bitness you're expecting when hitting "Change...", check the machine.config information for your targetted framework.

[Former Member]

Thanks, but that's not it. It works correctly in VS2008 and vs2010, just not in VS2013. When I ran setupvspackage.exe /I, it reported that it was successful for Visual Studio 2008 and Visual Studio 2010, but it never mentions 2013. I'm assuming it must be doing something to each instance of Visual Studio.

Harry

[jeff_albion]

Thanks, but that's not it. It works correctly in VS2008 and vs2010, just not in VS2013.

Ah, sorry about that - I somehow missed that information. We have not yet released support for Visual Studio 2013 / .NET 4.5.1 / Entity Framework 6.0. The last support we have released was for Visual Studio 2012 / .NET 4.5 / Entity Framework 5.0 (see CR #724639). We are still currently working on this support, with no provided ETA.

I'm assuming it must be doing something to each instance of Visual Studio.

Well, it's not specific to Visual Studio specifically (although that's what it will say on the output window when registering). It's really just registering the provider into <DbProviderFactories> in the any detected .NET framework's machine.config information.

successful for Visual Studio 2008 and Visual Studio 2010, but it never mentions 2013.

Do we try 'Visual Studio 2012'?

We will only currently detect up to Framework 4.5 with SetupVSPackage.exe (as mentioned above, if you're on 12.0.1.3817 or later). So, if you're attempting to target Framework 4.5.1 in your VS2013 project with the SQL Anywhere 4.5 provider, you may have to possibly edit the relevant 4.5.1 machine.config information yourself to have it currently appear in VS2013 as a registered provider. (I believe this is just the usual 4.5 configuration information, although I don't have 4.5.1 installed just quite yet so I can't quickly check.)

[Former Member]

I'm in the same boat as the OP, using Entity Framework 4.5 with VS 2013. It's now July, and this thread dates back to March. Is there any update on the status of VS 2013 support? Hopefully, it'll be available before MS releases VS 2014 or 2015 . . . (just kidding. . . I hope!)

[Former Member]

Support for VS2013 should be present in the next SQL Anywhere SP (16.0.0.1954+ and 12.0.1.4128+)

[jeff_albion]

Mikel is correct and VS2013 support will be released shortly - however, Entity Framework 6 (EF6) is still NOT supported.

The Visual Studio 2013 support that is to be released is limited to picking SQL Anywhere as a "Connection" as a Connection Source, etc.

Attempting to use the EF6 Tools in Visual Studio 2013 (even after targetting EF5 in the EF6 tooling) will result in an error retrieving the information against the database.

We are still working on providing support for EF6 (including the EF6 Tools).

[Former Member]

Jeff -- Any update on VS 2013 support for EF? I know that EF6 support was released recently. How about VS 2013?

[jeff_albion]

Visual Studio 2013 Integration Support was released in CR #766115, in 12.0.1.4128 and 16.0.0.1954. The support packages 12.0.1.4104 (SP72) and 16.0.0.2003 (SP18) are currently available on the SAP Support Portal.

As mentioned previously, (full) EF6 support is released in CR #770760, in builds 12.0.1.4162 and 16.0.0.2014, and are in the process of being built and tested.

[jack_schueler]

I believe the drop-down is showing .NET ... for SQL Server. Have you tried "<other>"?

[Former Member]

It is there but it says that "use this provider to connect to Microsoft Sql Server 2005 or above, or to SQL Azure" so i think it is not for SQL Anywhere.

[jack_schueler]

When you pick other, what does the Data provider drop-down list show? (Click v)

For example, I see things like:

  .NET Framework Data Provider for ODBC
  .NET Framework Data Provider for OLE DB
  .NET Framework Data Provider for Oracle
  .NET Framework Data Provider for SQL Anywhere 12
  .NET Framework Data Provider for SQL Server