You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am attempting to migrate a Xamarin native (Xamarin.iOS and Xamarin.Android) solution from MVVMLight to CommunityToolkit.Mvvm.
I have pored over documentation on this topic here. The docs state that
there are no replacements for platform-specific components
My question (and request for added documentation) is: what are the options for addressing this gap in functionality? Specifically, I am looking for a way to programmatically bind observable properties to native control instances (previously provided by the Binding, BindingMode, etc. classes and extension methods in MMMVLight).
Are there any projects that attempt to fill this gap?
Is this functionality relatively trivial to implement from scratch?
Or is what I'm trying to do (use CommunityToolkit.Mvvm with a Xamarin native codebase) inherently misguided?
Thanks so much for any guidance, and consideration to augment the docs on this topic!
The text was updated successfully, but these errors were encountered:
Following up to see if I can get any help or hints. How are folks approaching the task of binding native control instances (ex. iOS UITextField or Android EditText) to observable properties on a VM class instance?
I am attempting to migrate a Xamarin native (Xamarin.iOS and Xamarin.Android) solution from MVVMLight to CommunityToolkit.Mvvm.
I have pored over documentation on this topic here. The docs state that
My question (and request for added documentation) is: what are the options for addressing this gap in functionality? Specifically, I am looking for a way to programmatically bind observable properties to native control instances (previously provided by the
Binding
,BindingMode
, etc. classes and extension methods in MMMVLight).Thanks so much for any guidance, and consideration to augment the docs on this topic!
The text was updated successfully, but these errors were encountered: