Loading...

Rx.NET v7.0 Released

Rx.NET v7.0 Released

In this video, Ian Griffiths announces Rx.NET 7.0, highlighting a potential 95MB reduction in application deployment size by moving UI framework support out of the main System.Reactive package into separate NuGet packages (System.Reactive.Windows.Forms, System.Reactive.Wpf, System.Reactive.Uwp, and System.Reactive.WindowsRuntime).

He explains the three breaking changes:

  • dropping .NET 6 and 7 support (now targeting .NET 8+ and tested on 8–10),
  • fixing a nullable annotation bug in OfType (no runtime change),
  • the UI-package split that prevents Windows TFMs from implicitly pulling in WPF/WinForms, which previously bloated self-contained deployments (example growing from 102MB to 197MB with Rx 6.1).

Rx 7.0 keeps binary compatibility by retaining UI code at runtime but hiding it from reference assemblies, with analyzers guiding developers to add the right package; he also recounts the historical "great unification" decision and invites feedback via GitHub for community suggestions of v8.0 features.

Full documentation is available at Introduction to Rx.NET.

  • 00:00 Rx.NET 7.0 Overview
  • 00:30 Breaking Change One TFMs
  • 01:51 TFM Confusion Explained
  • 03:18 Breaking Change Two Nullability
  • 04:37 Big Change UI Packages Split
  • 07:21 Demo The 95MB Problem
  • 12:51 Rx 7 Deployment Results
  • 15:14 Source vs Binary Breaking
  • 18:10 ReactiveUI Still Works
  • 22:34 Why This Happened
  • 26:22 Wrap Up Next Steps

Published on:

Learn more
endjin.com
endjin.com

We help small teams achieve big things.

Share post:

Related posts

Stay up to date with latest Microsoft Dynamics 365 and Power Platform news!
* Yes, I agree to the privacy policy