The library is designed with XAML in mind and I get the concept around the string identifier for multiple DialogHost instances. However, I do a lot of code-based (or at least non-MVVM) work, and usually I have a (reference to a) DialogHost instance. I would like to invoke a dialog directly on that instance.
This PR adds additional (static) DialogHost.Show() overloads, which are taking a DialogHost instance in place of the string identifier. You can then open a dialog on an instance by calling
The library is designed with XAML in mind and I get the concept around the string identifier for multiple
DialogHost
instances. However, I do a lot of code-based (or at least non-MVVM) work, and usually I have a (reference to a)DialogHost
instance. I would like to invoke a dialog directly on that instance.This PR adds additional (static)
DialogHost.Show()
overloads, which are taking aDialogHost
instance in place of the string identifier. You can then open a dialog on an instance by callingNote: I also fixed a typo in
identifier
and removed redundant async/await keywords.