Using ReactiveUI along with MVVMToolkit

[ComtelJeremy]

We use a very hybrid (and probably strange) approach to several apps. We use Prism for the base framework, and have added quite a bit of ReactiveUI for UI logic, properties, etc.
We also started using MVVMToolkit, which is MS supported and works very well to save all the private/public field/property boilerplate on INotify properties. This was before ReactiveUI had much or anything for source generation.
We have now run into a little snag, as we can't use the source generation from MVVM toolkit for anything with ReactiveObject as the base class as it can't find/use the ReactiveUI implementations.
See CommunityToolkit/dotnet#620 (comment) for some more background.
Any suggestions on how best to work around this, would be appreciated. Am I missing something in ReactiveUI that could replace MVVMToolkit for simple properties that need to be observed? Perhaps there has been some work I missed since digging into this last.
Thanks in advance for any suggestions.

[glennawatson]

Can’t see why you can’t use both toolkit and our generators is one option.