WPF ObservableCollection vs List Problem
-
I'm working on a WPF app. The DAL is behind an MVC 4 WebAPI hitting SQL. I have a one-to-many collection of Addresses & phones. The Address object contains a list of Phone objects. Each address can contain one or many phones. If I create the phone list using List then the UI doesn't see new phones when added. If I create the list using ObservableCollection then when I return the collection from the DAL the phones list is null. The list of phones doesn't serialize coming back from through the API. What's wrong here? What's the right way to do this?
If it's not broken, fix it until it is
-
I'm working on a WPF app. The DAL is behind an MVC 4 WebAPI hitting SQL. I have a one-to-many collection of Addresses & phones. The Address object contains a list of Phone objects. Each address can contain one or many phones. If I create the phone list using List then the UI doesn't see new phones when added. If I create the list using ObservableCollection then when I return the collection from the DAL the phones list is null. The list of phones doesn't serialize coming back from through the API. What's wrong here? What's the right way to do this?
If it's not broken, fix it until it is
I would try to add the serialize attribute to the data-model you mentioned. No sense trying to resolve the WPF part until the data-model part is working from your API. Then I would create a view-model class to separate the data-model class from the WPF window. Add the INotifyProperty pattern to the view-model. And then in xaml, make sure to reference the name of the public properties in your view-model for the collections; like your OC.
Ben Scharbach Temporalwars.Com YouTube:Ben Scharbach
-
I would try to add the serialize attribute to the data-model you mentioned. No sense trying to resolve the WPF part until the data-model part is working from your API. Then I would create a view-model class to separate the data-model class from the WPF window. Add the INotifyProperty pattern to the view-model. And then in xaml, make sure to reference the name of the public properties in your view-model for the collections; like your OC.
Ben Scharbach Temporalwars.Com YouTube:Ben Scharbach
You replied to a message from 3 years ago???
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.