microsoft-ui-xaml icon indicating copy to clipboard operation
microsoft-ui-xaml copied to clipboard
verified publisher icon microsoft

Proposal: Supported old INotifyPropertyChanged and IValueConverter interfaces

Open jaigak opened this issue 4 years ago • 4 comments

Many code have been written to use Windows.UI.Xaml.Data.INotifyPropertyChanged and Windows.UI.Xaml.Data.IValueConverter. With WinUI 3, these interfaces can't be used as it only knows about Microsoft.UI.Xaml.Data.INotifyPropertyChanged and Microsoft.UI.Xaml.Data.IValueConverter respectively. These interfaces are exactly the same except the GUID, so why not let them be used for data binding and for converters along with Microsoft.UI.Xaml.Data.INotifyPropertyChanged and Microsoft.UI.Xaml.Data.IValueConverter? This will save a lot of migration work.

jaigak avatar Apr 11 '21 05:04 jaigak

@MikeHillberg FYI

StephenLPeters avatar Apr 12 '21 23:04 StephenLPeters

This will also allow to use System.ComponentModel.INotifyPropertyChanged in C# as .NET Native maps it onto Windows.UI.Xaml.Data.IValueConverter.

jaigak avatar May 04 '21 11:05 jaigak

I think it's better to get rid of the new interfaces as they are identical and don't refer other WinUI 3 types. Same way many enums and interfaces that don't refer WinUI 3 types are available on 1809+ in the system Windows.UI.Xaml namespace but they have been unnecessarily duplicated.

jaigak avatar Oct 20 '21 14:10 jaigak

Can someone clarify what do I do with Windows.UI.Xaml.Data.IValueConverter these days?

lostmsu avatar Sep 30 '24 04:09 lostmsu