SQL Anywhere 17 with ADO.net entity framework for Visual Studio 2019/22?

[vlad1]

Hi,

We are having problem with SQL Anywhere 17 (latest build) and ADO.Net entity framework in Visual Studio 2019 - we are trying to set up the EF provider with Visual Studio 2019. I believe we managed to do it for Visual Studio 2012 (with SQL Anywhere 11, not Anywhere 17), but we would really like to do it with Vis Studio 2019 or 2022 for SQL Anywhere 17.

Is this even supported in SQL Anywhere 17? ADO.net E framework provider for Vis Studio 19/22, and if not, can we expect it in futures patches and updates?

Thanks

[chris_keating]

SQL Anywhere supports the Entity Framework but it no longer provides integration starting with Visual Studio 2017.

[vlad1]

Thanks Chris, but is this likely to change in future updates, or in SQL Anywhere 18? Seems fairly limiting to have this just down to VS 2017?

[former_SQLA_member1694879]

If you use DBFactoryProvider you can build a class that works with VS 2022 and connects to SA17. It's not point and click but you can easily develop apps using this method.

[former_SQLA_member1695061]

There is dotconnect for Mysql that supports Visual studio 19/22, you can check it.

[awitter]

This only connects with odbc, not native. So this is not for performance

[vlad1]

No official or just unofficial rumours on this?

[axel_siepmann]

There will be no SA18 and no future updates regarding Entity Framework, i'm afraid.

[VolkerBarth]

Axel, how do you know that? Is there any official information on that?

[axel_siepmann]

No i don't. It's just guess respectively an apprehension. But isn't there an "end of support" for 2025 or 2027?

[VolkerBarth]

Well, then I think one should not make such bold statements but point out the guesswork...

The EOL for V17 has been discussed in this forum several times, e.g. here as the EOL has been updated now and then to further dates.

Note: I'm just another customer so I can only guess, too.

[axel_siepmann]

As i wrote: "i'm afraid..."

[VolkerBarth]

Ah, as a non-native speaker I've read that as "I'm afraid to tell you" or "unfortunately", not as "as I suspect". 🙂

[axel_siepmann]

Das ist natürlich immer schwierig, sich entsprechend auszudrücken, wenn man kein "native speaker" ist. Bin ich ja auch nicht. 😉