Rx.NET 7: Smaller Deployments for Windows Apps

Optimizing Rx.NET for Modern Deployments

Rx.NET 7.0's primary innovation lies in its pragmatic approach to reducing the deployment footprint of Windows applications. By decoupling UI-specific integrations like WPF, Windows Forms, UWP, and Windows Runtime into separate NuGet packages, developers no longer inadvertently pull in tens of megabytes of unused framework dependencies, particularly impactful for self-contained and Native AOT deployments. This targeted refactoring addresses a long-standing pain point for .NET developers concerned with application size and efficiency. The maintainers' effort to preserve binary compatibility while enforcing stricter compile-time dependencies through reference assemblies is a commendable feat, ensuring a smoother upgrade path for existing projects. The inclusion of a source analyzer to guide developers toward the correct new packages further enhances usability. This move aligns with the broader trend in .NET development towards more modularity and optimized deployment strategies, making Rx.NET a more attractive option for resource-constrained environments or scenarios where minimizing binary size is paramount. The fact that this significant improvement was achieved through focused maintenance rather than extensive new feature development underscores the value of dedicated technical debt reduction and modernization efforts in mature libraries.

Key Points

• Rx.NET 7.0 significantly reduces deployment size for Windows applications by separating UI integrations (WPF, Windows Forms, UWP, WinRT) into distinct NuGet packages.
• This addresses a common issue where self-contained applications could include large, unused framework dependencies, potentially saving tens of megabytes.
• The release focuses on modernization and technical debt reduction, continuing the stewardship by endjin.
• Binary compatibility is largely preserved, with older UI APIs remaining in runtime assemblies, while new compilations enforce explicit dependencies.
• A source analyzer is included to help developers identify and add the necessary UI-specific packages.
• Rx.NET 7.0 drops support for .NET 6 and .NET 7, while continuing support for .NET 8+, .NET Framework 4.7.2, .NET Standard 2.0, and UWP.
• Nullability annotations for OfType have been corrected, necessitating a major version bump under semantic versioning.
• Projects using the older packages.config mechanism may still include UI APIs without explicit new package references; this configuration is not supported.

---

📖 Source: Rx.NET 7.0 Reduces Deployment Size by Splitting Windows UI Support