TeärvisusAug 13, 2025

Update on the future of Rx.NET versioning:
https://github.com/dotnet/reactive/discussions/2211

The 3 scenarios that seemed to prevail:

1. Keep the System.Reactive packages. Solve problems using hacks (different API surface in build time than in runtime).

2. Introduce System.Reactive.Net packages, keep System.Reactive as a facade.

3. Try the first one in Rx7. If (when?) something breaks, switch to the second one.

A YT summary:
https://www.youtube.com/watch?v=GSDspWHo0bo

#dotnet #rx #rxnet #reactive #reactiveprogramming

Packaging Plans July 2025 · dotnet reactive · Discussion #2211

Our previous announcement that we were going to be moving forward with a new packaging plan for Rx.NET turned out to be premature. The plan, whose main goal is to fix the 'deployment bloat' issues ...

GitHub
TeärvisusJul 3, 2025

The State of Rx.NET in 2025

https://www.youtube.com/watch?v=SZpmj0fSfFI

tl;dw:

- Still living in dependency hell. They won't release Rx7.0 before solving those issues first. Everything else has lower priority.

- AsyncRx.NET will be developed over time.

- Ix.NET will not be developed as a part of the Rx project anymore. All LINQ to IAsyncEnumerable stuff will be moved to the core dotnet libraries.

#rx #rxnet #reactive #reactiveextensions #reactiveprogramming #dotnet #csharp #fsharp

The State of Rx.NET in 2025

YouTube
Matthew AdamsMay 23, 2024

An interesting post from Howard #endjin using #rx to observe file system changes. https://endjin.com/blog/2024/05/observe-file-system-changes-with-rx-dotnet

@idg10 does a deep dive into the Quiescent operator in our free ebook on RX.

https://introtorx.com/chapters/key-types#linq-operators-and-composition

#dotnet #reactive #rxnet

Observe File System Changes with Reactive Extensions for .NET | endjin

Use Reactive Extensions for .NET to transform FileSystemWatcher events into a powerful and easy-to-use event stream to deal with file system idiosyncrasies.

Angel MunozJul 13, 2023
Today I don't have any F# bits as I was in a bunch of meetings so... Let's feature another F# library!
Today we have : Fsharp.Control.Reactive
https://github.com/fsprojects/FSharp.Control.Reactive
If you like rxjs/rxjava/rxnet then this is a library to look after!
It enables reactive functional programming over observables and subjects, I personally love this library quite a lot ☕

#fsharp #dotnet #rx #frp #functionalreactiveprogramming #reactive #rxjs #rxnet
GitHub - fsprojects/FSharp.Control.Reactive: Extensions and wrappers for using Reactive Extensions (Rx) with F#.

Extensions and wrappers for using Reactive Extensions (Rx) with F#. - GitHub - fsprojects/FSharp.Control.Reactive: Extensions and wrappers for using Reactive Extensions (Rx) with F#.

GitHub
Andrew Nosenko 🇺🇦 🇦🇺Mar 22, 2023

Loving Rx.​NET interoperability with Tasks.

Below, I could turn each event subject into a Task and use Task.WhenAny instead of Merge (I still prefer the latter).

In other cases I do filtering, throttling, debouncing on a merged stream of events.

#rxnet #dotnet #reactivex

GiusepeNov 24, 2022
It’s alive!
Well, kinda… I still need to figure out the images, improve the layout, and fix the navigation.
But this is already my first #dotnetmaui + #rxnet project :) (Not THAT different from #xamarinforms, but there are a fill things to learn)
uvok cheetah 🇩🇪Jan 18, 2019

I wanted to add System.Reactive to a .Net Framework 4.6.2 application.
Suddenly I get hundreds of System.* dlls in the bin directory. Internet research said something about somethingsomething .net standard shims mumblemumble.

I have no idea what that means or what I can do against it. Retargeting to 4.7.2 as mentioned in some github issues is not an option.

The main dependency pulling in this stuff seems to be System.Threading.Tasks.Extensions

#rxnet #reactive