Click here to Skip to main content
11,648,094 members (60,859 online)
Click here to Skip to main content

List vs ObservableCollection vs INotifyPropertyChanged in Silverlight

, , 21 Sep 2009 CC (ASA 2.5) 211.9K 4.5K 103
Rate this:
Please Sign up or sign in to vote.
This article gives a basic understanding of List, ObservableCollection, and INotifyPropertyChanged.

Introduction

This article describes the basic understanding between List, ObservableCollectionand INotifyPropertyChanged.

Difference between List<T>, ObservableCollection<T> and INotifyPropertyChanged

List<T>

It represents a strongly typed list of objects that can be accessed by index. It provides methods to search, sort, and manipulate lists. The List<T> class is the generic equivalent of the ArrayListclass. It implements the IList<T>generic interface using an array whose size is dynamically increased as required.

Drawbacks

In ASP.NET, we simply use DataSourceand DataBind()to bind the data, but in Silverlight it is slightly different. Databinding in ASP.NET is done in a stateless way - once that binding operation is completed, it's a done deal and if you want to change anything, you have to manipulate the underlying controls that were created as a result of the data binding, or else change the underlying data objects and call DataBind() again. That’s what we are used to – but it’s not a good practice.

listgrid.JPG

In the sample application, the values in the list are added, removed and changed during runtime in the code behind. The changes in the list will not be updated to the UI (Datagrid).

ObservableCollection<T>

ObservableCollectionis a generic dynamic data collection that provides notifications (using an interface "INotifyCollectionChanged") when items get added, removed, or when the whole collection is refreshed.

Note: WCF service proxy class in Silverlight will use this type of collection by default.

observablecollection.JPG

Drawbacks

It does not provide any notifications when any property in the collection is changed.

observablecollectiongrid.JPG

In the sample application, the values in the observable collection are added, removed and changed during runtime in the code behind. The operations (adding and removing an item) in the observable collection will be updated to the UI (Datagrid). But any change in the existing item will not be updated to the UI.

INotifyPropertyChanged

INotifyPropertyChangedis not a collection, it’s an interface used in the data object classes to provide PropertyChangednotification to clients when any property value gets changed. This will allow you to raise PropertyChangedevent whenever the state of the object changes (Added, Removed, and Modified) to the point where you want to notify the underlying collection or container that the state has changed.

inotifypropertychanged.JPG

inotifypropertychangedgrid.JPG

INotifyPropertyChangedis compatible on all type of collections like List<T>, ObservableCollection<T>, etc. The code snippet which uses INotifyPropertyChangedis shown below:

public class UserNPC:INotifyPropertyChanged
{
    private string name;
    public string Name { 
        get { return name; } 
        set { name = value; onPropertyChanged(this, "Name"); } 
    }
    public int grade;
    public int Grade { 
        get { return grade; } 
        set { grade = value; onPropertyChanged(this, "Grade"); } 
    }

    // Declare the PropertyChanged event
    public event PropertyChangedEventHandler PropertyChanged;

    // OnPropertyChanged will raise the PropertyChanged event passing the
    // source property that is being updated.
    private void onPropertyChanged(object sender, string propertyName)
    {
        if (this.PropertyChanged != null)
        {
            PropertyChanged(sender, new PropertyChangedEventArgs(propertyName));
        }
    }
}

In the above code snippet, whenever a value is set to a property, the method “onPropertyChanged” will be called which in turn raises the PropertyChangedevent.

History

  • 22nd September, 2009: Initial post

License

This article, along with any associated source code and files, is licensed under The Creative Commons Attribution-ShareAlike 2.5 License

Share

About the Authors

BalaG Ganesan
Technical Lead Infosys
India India
Working as a Technology Lead in Infosys at Chennai, India.

Venkatesan Jagadisan
Software Developer iSOFT
India India
Working as a Software Engineer in iSOFT at Chennai, India.

You may also be interested in...

Comments and Discussions

 
GeneralGood Article Pin
akhilesh saini19-Jul-12 5:43
memberakhilesh saini19-Jul-12 5:43 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Terms of Use | Mobile
Web04 | 2.8.150804.4 | Last Updated 22 Sep 2009
Article Copyright 2009 by BalaG Ganesan, Venkatesan Jagadisan
Everything else Copyright © CodeProject, 1999-2015
Layout: fixed | fluid