Dropping the .NET Framework solution

[tomkirbygreen]

Currently we build both .NET Standard and .NET Framework. If we where to say that the minimum version of .NET Framework we supported was 4.7.2 (released 30 April 2018) then we could drop explicit support for .NET Framework as a separate solution within the ably-dotnet SDK and just use the .NET 'Standard' assembly to target both 'legacy' .NET Framework (4.7.2 and above) and .NET going forwards.

In doing this we could simplify the project structure by dropping the .Shared projects.

Of course doing this would require that we could take complete control of our AssemblyVersion such that the first unified release of ably-dotnet would be versioned 2.0.<build number>.<revision> .

┆Issue is synchronized with this Jira Uncategorised by Unito

[tomkirbygreen]

I now don't think we can completely drop support for the legacy .NET Framework implementation so long as said implementation is shipped as a built-in component of the versions of Windows we support.

We should however look to update all .NET Framework specific dependencies to require .NET Framework 4.8 as their required minimum supported runtime version. .NET Framework 4.8 marks the official end from Microsoft's perspective of innovations within .NET Framework, all attention now being on .NET 6 and .NET 7.