|
Does anyone know if there are plans on supporting .NET Core in the future? If not, and the sqlanywhere folks are reading this, this is a +1 to a request for support. Reason: Quite a few of our projects use .net services to perform various tasks. A lot of these services are not windows specific other than using .NET 4.5+ and SQL Anywhere, so to provide more flexibility to our customers I've started to investigate whether .NET core is an option. Also fwiw, I note our usage of the .NET api for sqlanywhere is quite limited. We only use iAnywhere.Data.SQLAnywhere.SAConnection and any classes that it returns/requires. |
|
Is there any news about? |
+1 for EF Core support. This is the official list of supported providers: https://docs.efproject.net/en/latest/providers/
We have been waiting for .NET Core 2.0 to be released as the prior version was both a little 'bare' and had no native support for VB.NET
Most of our current sites run on .NET 4.6.1 and either use the V4.5 (Policy.17.0.SAP.Data.SQLAnywhere.v4.5.dll)provider directly or though a web service that that uses the V4.5 provider...
As the MS documentation is a little confusing as to whether Core runs on 4.6.1, or alongside it, or some totally different arrangement I am given to believe that the V4.5 provider will also work with Core. Is that the case? Has anyone tested this yet?
We will be installing Core 2.0, and VS support for it, this Saturday whilst running the latest patch Tuesday updates. We then intend to re-write some of the older WebForms sites and update existing MVC ones
+1 from me