Here. I can't believe a missed the first piece of Ian Griffiths's new column! Ian is a DevelopMentor instructor, co-author on three books with me (two still in development) and a long-time friend. Check out his opinion on WinFX and what it means for developers and please point me at the RSS feed so I don't miss the next one!

Here. FTP has posted the Design-Time Integration chapter from Windows Forms Programming in Visual Basic .NET. Enjoy.

Here. Of course, consumers won't care that the Electronic Showbox photo organization, editing and sharing software was built from the ground up using the .NET Framework (and Genghis), but I understand from the CTO that he "shudders" to think what it would have been link to develop in native code. Plus, he gives free copies to his favorite bloggers. Enjoy.

If you're overwhelmed by the huge number of PDC talks, I've split out the Longhorn-specific talks, including streaming video presentations, slides and demo source code as available.

Adam Kinney seems to be that rare combination of graphic designer and coder that I want to be to survive in the brave new world of Longhorn. I’m following his blog avidly.

Drew Marsh describes the internals of the XAML dotted attribute syntax that I described a few days ago as well as contrasting it with the existing .NET IExtenderProperty model.

Here.

Drew’s documenting what he discovers as he digs into Avalon.

Don Box simplified my XAML code using resources and styles. He also illustrates another XAML-ism that I’m coming to love: dotted element names. When you see something a dotted element name in XAML:

<GridPanel>
  <GridPanel.Resources>...</GridPanel.Resources>
  ...
</GridPanel>

what you’re looking at is a more convenient way of specifying an XML attribute using XML element syntax. For example, while you can specify a menu item like s

<MenuItem Header="New" />

However, if you’re doing anything fancy, like specifying an access key, you can do this using the dotted element name syntax:

<MenuItem>
  <MenuItem.Header>
    <FlowPanel>
      <AccessKey Key="N" />
      <SimpleText>ew</SimpleText>
    </FlowPanel>
  </MenuItem.Header>
</MenuItem>

In the first case, we’re just specifying a string, so declaring the Header attribute inline makes sense. In the second case, we’re composing the Header for the MenuItem as a FlowPanel, combining an AccessKey and a SimpleText element. Underneath the covers, XAML attributes translate into properties, so for those properties more complicated than strings, the dotted element name syntax allows properties to be specified as sub-elements.