System 4.0.0.0 System.Collections.ObjectModel.Collection<T> T System.Collections.Specialized.INotifyCollectionChanged System.ComponentModel.INotifyPropertyChanged System.Runtime.CompilerServices.TypeForwardedFrom("WindowsBase, Version=3.0.0.0, PublicKeyToken=31bf3856ad364e35") To be added. In many cases the data that you work with is a collection of objects. For example, a common scenario in data binding is to use an such as a , , or to display a collection of records. You can enumerate over any collection that implements the interface. However, to set up dynamic bindings so that insertions or deletions in the collection update the TLA2#tla_ui automatically, the collection must implement the interface. This interface exposes the event, an event that should be raised whenever the underlying collection changes. TLA2#tla_winclient provides the class, which is a built-in implementation of a data collection that implements the interface. Before implementing your own collection, consider using or one of the existing collection classes, such as , , and , among many others. If you have an advanced scenario and want to implement your own collection, consider using , which provides a non-generic collection of objects that can be individually accessed by index. Implementing provides the best performance with the data binding engine. To fully support transferring data values from binding source objects to binding targets, each object in your collection that supports bindable properties must implement an appropriate property changed notification mechanism such as the interface. For more information, see "Binding to Collections" in Data Binding Overview.

Notes on XAML Usage

can be used as a XAML object element in TLA#tla_winclient, in versions 3.0 and 3.5. However, the usage has substantial limitations. must be the root element, because the x:TypeArguments attribute that must be used to specify the constrained type of the generic is only supported on the object element for the root element. You must declare an x:Class attribute (which entails that the build action for this XAML file must be Page or some other build action that compiles the XAML). is in a namespace and assembly that are not initially mapped to the default XML namespace. You must map a prefix for the namespace and assembly, and then use that prefix on the object element tag for . A more straightforward way to use capabilities from XAML in an application is to declare your own non-generic custom collection class that derives from , and constrains it to a specific type. Then map the assembly that contains this class, and reference it as an object element in your XAML.