Rx.NET 7.0 reduces deployment size by splitting Windows UI support into modular packages, according to the official .NET Blog release notes published on November 14, 2022. The update addresses long-standing bundle size bloat for developers building cross-platform applications with Reactive Extensions for .NET.
Modular Architecture and Windows UI Separation
According to the .NET Blog, the core Rx.NET 7.0 release separates platform-specific Windows presentation libraries from the main framework binaries. Developers working on non-UI projects, server-side applications, or console tools no longer pull down heavy Windows Presentation Foundation (WPF) and Windows Forms dependencies by default. This refactoring trims unnecessary binary weight from modern cloud and background services.
Microsoft engineering teams structured the 7.0 release to isolate platform primitives. Projects requiring UI integration now reference explicitly named NuGet packages. That architectural shift prevents unintended code inclusion during builds, keeping container images lean for microservices architectures.
Deployment Size Reductions and Performance Metrics
According to release telemetry shared by the .NET Blog, trimmed application deployments see direct byte-count reductions when omitting unused UI schedulers. Applications running on Linux or macOS containers benefit immediately by avoiding unnecessary Windows desktop libraries in their dependency trees.
Performance overhead also decreases during application startup. With fewer assemblies loaded into the application domain, JIT compilation times improve marginally for large enterprise solutions leveraging reactive streams.
Migration Path and Breaking Changes
Upgrading from Rx.NET version 5 or 6 requires explicit namespace and package adjustments. According to the official migration documentation, developers must add dedicated NuGet packages such as System.Reactive.Windows.Threading if their codebase relies on dispatcher schedulers tied to WPF or Windows Forms loops.
- Core Library: Remains lightweight and universal across all target frameworks.
- UI Extensions: Moved to separate, opt-in NuGet packages.
- Target Frameworks: Full support for .NET 6, .NET 7, and .NET Standard 2.0.
Frequently Asked Questions
Does Rx.NET 7.0 support older .NET Framework versions?
According to Microsoft’s release notes, Rx.NET 7.0 targets .NET Standard 2.0 and modern .NET runtimes, maintaining backward compatibility for older framework consumers where applicable.
Do I need to change my reactive query code when upgrading?
Standard LINQ query operators and observable sequences remain syntactically identical. Only project files requiring UI thread dispatching need explicit package additions.
Worth a look