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 ;)

After waiting literally 7 years to upgrade my laptop, I finally purchased a Dell Studio laptop last night. With it's 9 cell battery, I get this lovely indicator in my system tray:

MSDN has a new low bandwidth version that is much much faster to use. Plus it doesn't have that frame on the left hand side that is always refreshing. It is currently in Beta, but I haven't seen anything that will prevent me from using it from here on out.

Another benefit, you can now click your middle mouse button and drag to scroll, which for some reason is broken in the regular MSDN website (it would only recognize the ability scroll horizontally)

Check it out here: http://msdn.microsoft.com/en-us/library/system.xml(loband).aspx

One note, though, if you want it to persist (which you will), you have to click the "Persist Low Bandwidth View" link in the upper right hand corner.

FYI - I'll be giving a "Tips and Tricks" presentation at the third Iowa Code Camp in Cedar Rapids on May 2nd. The first two camps have been awesome, I highly recommend coming if you get a chance.

www.IowaCodeCamp.com

I'm giving a WPF talk at IADNUG meeting tonight if anyone is interested. It is at 5:45 at DMACC West. Come for the pizza, stay for the fat guy making self-deprecating jokes.

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!

I found this in the comments on CodingHorror (http://www.codinghorror.com/blog/archives/001145.html#comments)

It shows what happens when no one takes the time to "reinvent the wheel". Bravo!

Original link (http://www.it-eye.nl/weblog/wp-content/uploads/2008/08/new-car-old-wheels.jpg) was posted by ako - http://www.andrejkoelewijn.com/wp/