Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Discussion options

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.

You must be logged in to vote

Replies: 1 comment

Comment options

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

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
🙏
Q&A
Labels
None yet
2 participants
Morty Proxy This is a proxified and sanitized view of the page, visit original site.