On a break from blogging at the moment, service will resume when my new MacBook Pro arrives (new resolution, faster CPU, nvidia chipset and 4gig of memory), and when I finally finish my move in central London. That said, my Silverlight predictions were accurate 100%, except I predicted a beta where both an RC and a CTP were released. And thanks to Brownie Points for enhancing my wpf snippets, although my blog is not notstatic.com and he forgot to give me credits. Hopefully he'll read the trackback and amend his entry. A lot could be said about the addition of UIPropertyMetadata against FrameworkPropertyMetadata. Rule of thumb if you're using WPF, unless you know the difference between the UIElement and the FrameworkElement levels, stick with the Framework layer. In this case, for WPF FrameworkPropertyMetadata is acceptable, for other toolkits only PropertyMetadata would be more accurate.

I was reading the wpfbox blog about the MIX07 announcement regarding Silverlight (the new name for WPF/E). Well if this is the one you're talking about, we've known for some time that wpf/e would include a derivative of the micro CLR that already ran on the short lived SPOT devices, and a lot of work has gone through enabling CLS compliant languages to run on an embbed version of the CLR. My best bet is that compiled IL will be presented at MIX07, together with a beta. Maybe there will even be full interop between IL code and javascript code, letting you call objects coded in C# using javascript.

Not from me, but from Neil, my future ex-colleague at Netstore: “Default” buttons in WPF and multiple default buttons per page.