MVVM/WPF: Using a ObservableCollection<T> as a list in a domain model, is that good/bad ?
Posted
by msfanboy
on Stack Overflow
See other posts from Stack Overflow
or by msfanboy
Published on 2010-05-21T18:00:51Z
Indexed on
2010/05/21
18:10 UTC
Read the original article
Hit count: 410
I have aggregated models like Customer:Order:Product.
As my View is bound to the BillingViewModel which has a Property Customers of type ObservableCollection
and ONE customer in this collection has a "list" of orders named ObservableCollection
and ONE order in this collection has a "list" of products named ObservableCollection
Well I need the ObservableCollection`s for databinding but should a domain model really have a ObservableCollection ? normally it has a
List or IEnumerable !
Is this bad habit or having side effects?
© Stack Overflow or respective owner