the web site says you can in .NET 4.0
I cant seem to do it though, what assesmbly references and xmlns' do i need
the following does not work
xmlns:coll="clr-namespace:System.Collections.ObjectModel;assembly=mscorlib"
<coll:ObservableCollection x:TypeArguments="x:Object">
<MenuItem Command="ApplicationCommands.Cut"/>
<MenuItem Command="ApplicationCommands.Copy"/>
<MenuItem Command="ApplicationCommands.Paste"/>
</coll:ObservableCollection>
ObservableCollection<T> is defined in the System assembly, so your namespace should read:
xmlns:coll="clr-namespace:System.Collections.ObjectModel;assembly=System"
You can find that information in MSDN at the top where it says:
Namespace: System.Collections.ObjectModel
Assembly: System (in System.dll)
XMLNS for XAML: Not mapped to an xmlns.
Note that the assembly has changed between v3.5 and v4.0. In v3.5 it was defined in the WindowsBase assembly. However, this was a drawback since you often would like to use the class without any WPF assemblies referenced. So maybe that is why they changed it.
Furthermore, you should also check this blog post, which says that the new XAML features are not completely available in VS yet!
I realize that this is an old question but I just came across the same problem while working on a Windows Store App. After several problems I figured out, that the easiest why to define such a collection in XAML is to simply create a subclass:
namespace my.name.space {
public class ObservableMyObjectCollection: ObservableCollection<MyObject> {
}
}
And then use it like so
<local:ObservableMyObjectCollection
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:local="using:my.name.space">
<MenuItem Command="ApplicationCommands.Cut"/>
<MenuItem Command="ApplicationCommands.Copy"/>
<MenuItem Command="ApplicationCommands.Paste"/>
<local:ObservableMyObjectCollection>
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With