Yes, our parser is automatically creating the collection when you populate the collection property in the xaml, so you don't have to explicitly write a node in the xaml with the collection type:

<Object>
<Object.List>
<!--ItemList--> <!-- This becomes optional -->
<Item/>
<Item/>
<Item/>
<!--/ItemList--> <!-- ... -->
</Object.List>
</Object>

And as long as the items are specified in the xaml, they are serialized with the collection in the xaml resource. Then, as you load the xaml, you already have those items added to the collection when the OnPostInit() gets called.

Is this behavior a problem?

You mean despite the fact that it works different in WPF? :P

Okay, to be more serious I have to think this through. The problem here was mainly that I expected a different beahviour and took me a while to figure out what's going on and why the CollectionChanged event was never called.

And I know there were problems/restrictions in v1.1 when you serialized other UserControls and / or collections so instead of this I changed everything so it was created dynamically.

I'll take another look at it and tell you how it went.

:)

It's just to prioritize tasks, if you can live with current behavior for a while, we can assign it a low priority.

Of course, the right thing is to behave exactly as WPF, and we will change this.

Leave it as is for now. Unfortunately before I can continue you have to fix #575 first or least tell me what's causing it so I may be able to circumvent it.