INFO: How long will Rebex support old versions of .NET Framework?

Summary

  • Rebex components for specific framework will be supported at least as long as Microsoft supports that framework.
  • Security fixes for Rebex components for specific framework will be released at least as long as Microsoft releases security fixes for that framework.

Rebex Support Lifecycle for various .NET Framework versions

Users of Rebex products get an access to dlls compiled for various .NET Framework versions (*1). This document describes for how long Rebex will continue support the specific framework version.

Rebex components support for specific framework version is synchronized with Microsoft's support for the framework version. Microsoft Main support phase lasts at least 5 years after the release of the .NET Framework version. Microsoft Extended support phase lasts for another 5 years. Read Microsoft Support Lifecycle Policy FAQ for details on Microsoft support phases.

Rebex Main Support phase for specific .NET Framework ends not sooner than Microsoft's Main Support phase. The Rebex Extended Support phase ends not sooner that Microsoft's Extended Support phase.

Following table summarizes support provided in the specific phases

Rebex support phases
Support provided Mainstream support phase Extended support phase
Security fixes (*6) For every customer For every customer
Non-security fixes Customers with support contract Customers with support contract, upon request
Trial packages For everyone -

Rebex binaries for specific platform

Following table shows availability of binaries targeted to specific platforms. Platform support is determined by Microsoft's support timelime for that platform. In other words - Rebex can provide binaries for a platform which is no longer supported by Microsoft. Even if you still get Rebex binaries, the support for platforms deprecated by Microsoft can be limited.

Platform code  Target platforms of the latest version Available from Available until Availability with Legacy Support
netstandard2.0 .NET Core 2.0-2.1 early 2019 2021-08-21  
netstandard1.5 .NET Core 1.0-2.1 2017-05-09 2020-01-01 Not decided yet
net-4.6 .NET 4.6-4.7.2 early 2019 2024-10-10 n/a
net-4.0 .NET 4.0-4.7.2 and Mono 2010-05-20 2023-10-10 2028-10-10
net-3.5 .NET 3.5 SP1 and Mono. early 2019 2023-10-10 2028-10-10
net-2.0 .NET 2.0, .NET 3.0, .NET 3.5, .NET 3.5 SP1 and Mono 2006-11-27 2020-01-01 n/a
net-1.0 .NET 1.0, .NET 1.1, .NET 2.0 2003-04-14 2010-03-11 n/a
netcf-3.9 .NET Compact Framework 3.9 2013-12-02 2019-07-01 2023-10-10
netcf-3.5 .NET Compact Framework 3.5 2009-01-12 2019-07-01 2021-04-13
netcf-2.0 .NET Compact Framework 2.0 2006-11-27 2017-05-09 2018-07-31
netcf-1.0 .NET Compact Framework 1.0, 2.0 2003-11-01 2010-03-11 n/a
xamarin.android Xamarin.Android 2013-12-02 2020-01-01 n/a
xamarin.ios Xamarin.iOS 2013-12-02 2020-01-01 n/a

Microsoft Framework support timeline

Version General Availability Date Support retired Extended support retired Latest Rebex component build
.NET 1.0 2002-04-15 2007-07-10 2009-07-14 build 3723 released on 2010-03-11
.NET 1.1 2003-07-10 2008-10-14 2013-10-08 build 3723 released on 2010-03-11
.NET 2.0, 3.0 and 3.5 (*2) 2006-02-17 2011-07-12 2011-07-12 current
.NET 3.5 SP1 (*3)   See Lifecycle FAQ - .NET Framework   current
.NET 4.0   2010-06-29 2015-07-14 2020-08-09 current
.NET 4.5-4.7.2 (*3)   See Lifecycle FAQ - .NET Framework   current
.NET CF 1.0 2003-07-10 2008-10-14 2013-10-08 build 3723 released on 2010-03-11
.NET CF 2.0 2005-10-31 2011-01-14 2016-04-12 Release 2017 R6.3 released on 2018-01-11
.NET CF 3.5 (*4) 2008-02-19 2016-04-12 2021-04-13 current
.NET CF 3.9 (*5) 2013-08-11 2018-10-09 2023-10-10 current

See also:

Notes

*1) Not all Rebex products are available for all framework versions. If the product for specific framework version is released it will be supported according to this document. However the release of component for specific framework is not guaranteed.

*2) .NET 3.0 and .NET 3.5 depends on .NET 2.0 CLR. Dates are based on Microsoft support phases for .NET 3.5 Framework.

*3) Beginning with .NET 3.5 SP1, .NET Framework is considered a component of the Windows OS. Components follow the Support Lifecycle policy of their parent product or platform.

*4) .NET CF 3.5 is part of Windows Embedded Compact 2007.

*5) .NET CF 3.9 is part of Windows Embedded Compact 2013.

*6) Security fixes are provided only for critical security vulnerabilitoes in Rebex code. However, this does not apply to vulnerabilities caused by weaknesses in protocols or algorithms themselves or in third party code.