Issue Details (XML | Word | Printable)

Key: DNET-774
Type: Task Task
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Jiri Cincura
Reporter: Jiri Cincura
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.
.NET Data provider

Drop NET40 support #breaking

Created: 25/Jul/17 08:14 AM   Updated: 06/Jun/18 11:47 AM
Component/s: ADO.NET Provider, Entity Framework, NuGet packages
Affects Version/s:
Fix Version/s:

Issue Links:

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Jiri Cincura added a comment - 25/Jul/17 08:17 AM

André Ziegler added a comment - 30/Jul/17 12:54 PM

I still need .net 40/XP compatibility until 2019 when support for Windows Embedded 2009 ends.

If you kill .net 4.0 and the provider has a serious issue (after .net 40 was killed) that may cause data corruption I can't update the the fixed version.

Also why do you discuss this on a site which noboby knows?

Jiri Cincura added a comment - 03/Aug/17 07:09 PM - edited
It's a standard mailing list that you can find on site. Exactly the place which everybody knows. And Nabble is a web mirror of that.

If you're willing to put money into supporting .NET 4, I can extend the lifetime of that (you can discuss your intention in the list, if you want). Else I just don't have enough free time to spend on .NET 4 and also all other versions.

André Ziegler added a comment - 07/Aug/17 02:00 PM
it is so well known that only 2 person replied to it. So I call this unknown place.

Also your statement that .net 4.0 no longer gets updated is wrong. Last .net 4.0 update is from June 2017:

June, 2017 Security Only Update for .NET Framework 4 on WES09 and POSReady 2009 (KB4021915)

Jiri Cincura added a comment - 07/Aug/17 07:50 PM
But that's a KB for XP Embedded. I'm pretty sure there's dozens of variations MS still supports. And will support for extended support customers. I don't have resources for that, sorry. But you can of course help with that as well. Helping hand is always welcome. Will you step in?

BTW, if you have a better place to discuss things, you're welcome to bring that up. So far the mailing lists and tracker is what Firebird project uses.

André Ziegler added a comment - 08/Aug/17 04:18 PM
I'm talking all the time about XP Embedded. Windows Embedded 2009 is based on Windows XP and XP only supports up to .net 4.0. 4.5 is not supported on XP, that is why I still need .net 4.0 support for 1 year.

Jiri Cincura added a comment - 16/Aug/17 07:23 AM
OK, one week from now I'll drop NET40 from 6.0 onward, unless somebody opens up a discussion here or in the list and contributes in any way for NET40 support.

André Ziegler added a comment - 21/Aug/17 07:24 AM
before dropping .net 40 support, move the .net 40 code into an extra maintain branch (5.x) and if later provider versions (6.x) include a fix for a serious issue, backport this to the 5.x branch. I don't need new features, I only need some kind of support until Microsoft drops .net 4.0 support for Windows Embedded systems that are based on XP in January 2019.

Jiri Cincura added a comment - 21/Aug/17 08:42 AM
That's already possible via IBPhoenix services ( I remember backporting some features to old .NET 2.0 versions.

André Ziegler added a comment - 22/Aug/17 05:47 AM
I don't want features, I only want fixes for blocking issues to .net 4.0 branch. I can do this on my own, but I need the .net 40 code, so please create a .net 40 branch before killing the code from master.

André Ziegler added a comment - 30/Aug/17 05:42 AM
so what are the plans now? can we get the extra branch for users who still (have to) care about .net 4.0 support for old XP Embedded systems?

Jiri Cincura added a comment - 30/Aug/17 05:49 AM
Yes. The 5.x version will be maintained with .NET 4 support, if needed. Current version is tagged 6.x will drop it.