Here. XAML is the Longhorn mark-up language for declaring object types and instances and hooking them up to code. While it's most often used for declarative Avalon UI, it's useful for more than that. In fact, one enterprising 3rd party has just released a beta tool that provides a XAML subset for .NET 1.1. It's not quite the same, but interesting never the less.

Here. The one where I declare an official, immediate need for all those unemployed web site designers to get to work on Avalon ASAP.

Here. SYS-CON interviewed me and a bunch of my friends at the PDC. It's somewhat painful to listen to me with a cold, but fun to listen to folks like Dan Appleman, Scott Hanselman, Chris Kinsman, Jeff Prosise, Ingo Rammer, Brent Rector, John Robbins, David Treadwell, Shawn Wildermuth and a whole bunch more.

Here. I'm going to save myself a lot of posts and just tell you now: if you're into Avalon, read Chris Anderson's posts.

Here. Chris Anderson, an architect on the Avalon team, talks about the history of the Avalon team, including how it was formed, the goals for Avalon and the rearchitecture a year before the PDC.

Here. While things will most definately change before VS.NET Whidbey is released, this document provides a great list of new features in both C# Whidbey and VC# Whidbey. And it's much more than generics, partial types, anonymous methods and iterators. [weblogs.asp.net/duncanma]

Here. To save myself linking to nearly every single one of his posts, I'll just tell you now: If you're doing WinFS or curious how it works or what it means, you *must* read Mike Deem's blog.

Here. If you haven't noticed, the Longhorn SDK site on MSDN [1] has a new area at the bottom of each page. We call the entries in this area "annotations." This area is broken up into three parts: 1. Microsoft "official" annotations, like what you'd find in a ReadMe, but associated with the specific piece of content itself 2. General group discussion, like in a newsgroup, but again, associated with the content itself 3. 3rd party annotations The 3rd part come from a client-side component that acts as an RSS aggregator, pulling annotations for a specific piece of content from the RSS feeds that you subscribe to via the component. O'Reilly was nice enough to provide an RSS feed at the launch of the annotations project to both demonstrate it's usefulness and provide real annotations to about 50 pieces of content on the Longhorn SDK. In addition, they've posted a nice article about how other 3rd parties can provide their own annotations via RSS to nestle at the bottom of the MS Longhorn SDK content. If you'd like to provide annotations for folks to subscribe to as "annotations," you can do so without any permission or special support from MS. If you'd like to be considered as a "Recommend" source of annotations, drop me an email: csells@microsoft.com. [1] http://longhorn.msdn.microsoft.com