You’ve probably seen this by now, but I thought I’d post the WinFX Nov05 CTP-related links together in a spot where I could find them later. In addition to being closer to what we plan on shipping, this CTP also works with VS05 RTM:

• WinFX Readme
• What’s New in WPF
• WinFX Runtime Components (WCF, WPF and WF)
• WinFX SDK
• VS05 Extensions for WCF and WPF
• VS05 Extensions for WF

Enjoy!

The WinForms team has put up all kinds of WinForms 2.0 resources, including a bunch of FAQs and samples. Enjoy.

Does anyone know if it's possible to turn off the special PC features of DVDs and CDs? I'd like to avoid Sony-sponsored virus enablers on CDs and required players for DVD content and just treat each of these CDs and DVDs as un-special. Is such a thing possible?

As an engineer, I appreciate the efficiency of combining the criminal and civil trials into one. Plus, if it weren't for "women who have inexplicably bad judgment," I'd never have reproduced. : )

If you could boot Windows Vista from a USB drive large enough for the OS and apps, like this version of Linux, and log into FolderShare for your data, you could use any computer that allowing booting from USB into a temporary terminal (although device drivers would be a challenge).

This is how you tell the marketing guys from the engineers… : )

Private email forwarded by Adam Denning

If I’ve got an Avalon Button, e.g.

<Button Content=“OK” />

Should I give the button a name so I can handle the event (I would never put the event handler directly in the XAML) like this:

<Button Content=“OK” x:Name=“okButton” />

Or, should I define a custom command and invoke it like this:

<Button Content=“OK” Command=“local:MyDialog.OkCommand” />

Defining a command seems like overkill (you do some stuff in the static ctor and some other stuff in the instance ctor), but I like consistency, e.g. my main window’s menu will use commands.

Thoughts on the best practice here?