My WPF Wish Has Come True. w00t

So a while back I posted a wish list of things that would change with WPF. It looks like the WPF has granted one of my wishes: INotifyCollectionChanged and ObservableCollection<T> are moving out of WindowsBase.dll and into System.dll!

(I know it was most likely other people that convinced them of this, but let me live it my bubble where my wants and needs are the only ones that matter)

Thanks Jamie!

http://blogs.msdn.com/jaimer/archive/2009/09/22/wpf-discussion-090922.aspx

WPF and XAML 4.0 Wishlist

Microsoft: Please Please Please add the following two things two the next WPF/XAML version.

Addition 1

Move ObservableCollection<T> and INotifyCollectionChanged to the system.dll instead of WindowsBase.dll. It is insanely annoying that I can't reuse my model objects in a web application without referencing WindowsBase.dll. It just feels dirty, plus it typically leads to hosting problems.

Addition 2

I understand that you'd want two different Color structures - one for WinForms and one for WPF. But it would make my life a lot easier if you created an IColor interface that simply had the byte properties A, R, G and B.

Having some native methods on the color objects to convert from HSL would be greatly appreciated too.

I'd be willing to pay a couple of dozen dollars for these two features, just let me know ;)

XAML Folding?

In the off chance that someone on the VS2010 team happens to read this post:

PLEASE PLEASE PLEASE give us a better way of folding (collapsing) XAML. Something like regions would be fine, or some sort of attached property or designer property that we can put on various elements that we want folded when we hit our "collapse to definitions" shortcut. Some stuff I want collapsed, some I don't, please help us out!