We are moving forward with our plans to modify how UI-framework-specific features are packaged in Rx.NET. This is the last chance to offer feedback on #2086
Back in November 2023, we announced that we intended to fix some long-standing problems by making changes to Rx.NET packaging.
In February 2024, we created PR #2086 which enumerated the various options under consideration (and described all the suggestions we'd had from the community since the initial announcement).
Also in February we created PR #2084 as a prototype showing how this change might look, with some changes in March in response to community feedback.
.NET 9.0 is due to ship very soon. We intend to produce a new Rx.NET release not long after that happens.
This new version seems like the right time to move forward with the packaging plan. The first phase is to make new UI-framework-specific Rx packages available. We will not remove anything from System.Reactive at this time, but will mark all UI-framework-specific types and methods as [Obsolete], beginning the process
(Note: Rx 6.0 will work on .NET 9.0—anyone using Rx 6.0 today won't need to upgrade just to be able to move to .NET 9.0. The motivation for a new Rx.NET release is mainly that .NET 6.0 will be going out of support. And a secondary motivation is that a lot of people don't really understand how TFMs work, and mistakenly think that the absence of a net8.0 target indicates a lack of support for .NET 8.0. In fact we've supported Rx 6.0 on .NET 8.0 since .NET 8.0 shipped. But we want to make it clear that .NET 6.0 will not be officially supported by Rx.NET once it is no longer supported by Microsoft. So Rx 7.0 will not offer net6.0 TFMs. We plan to offer netstandard2.0, net472, net8.0, net8.0-windows10.0.19041 and uap10.0.18632.)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4