Factor ObservableObject into separate assembly about dotnet HOT 4 CLOSED

What problem do you think doing this would solve?

from dotnet.

As stated, I like having the observability, even the messaging, without needing the WPF aspects. Which obviously the WPF XAML aspects would not fit in terms of a Windows Service project. But the observability could.

from dotnet.

What WPF aspects? The MVVM Toolkit doesn't reference WPF at all. But also, I asked you what problem would this solve. You replied saying "I like ...". That's not a problem being solved.

from dotnet.

I may be confusing the CommunityToolkit.Mvvm.Input namespace, IRelayCommand pattern in particular. I suppose there's nothing about that which would be all that incongruent in another context, i.e. a Windows Service application. Closing for now, my apologies for the confusion.

from dotnet.