Here.

Rich Turned, an Indigo PM, has some useful things to say about Indigo in his recent Channel9 videos:

• What is the biggest misperception of Indigo?
• What is your advice to developers who are thinking about Indigo and interoperability?
• What would be the first thing about Indigo that you’d show a Visual Basic programmer?

Plus, Rich has a blog to which I subscribe (but I wish he were more prolific).

I’m really loving Jon’s approach to exploring and questioning the goals and implications of Longhorn:

1. Questions about Longhorn, part 1: WinFS
2. Questions about Longhorn, part 2: WinFS and semantics
3. Questions about Longhorn, part 3: Avalon’s enterprise mission

I don’t have any pithy summaries of his basic points; his posts deserve a read and a think.

This post is an oldie, but a goody, in which Kenny Lim talks not only about custom Avalon controls catching property changes so that they can re-render themselves, but also about the custom measurement sequence, which is a core piece of a control that does custom layout like, say, a pile of cards (hypothetically, of course : ).

VisitorVille maps your real-time web site data to a SimCity-like environment that you can use to see where folks are going on your site and how they’re navigating from one place to another. It does the other web traffic kinds of analysis, too, but the ability to watch your visitors in real-time looks pretty darn cool. This is the kind of thing that Longhorn should be good at enabling.

[via Jason Whittingon]

Richard Turner, a PM on the Indigo team, addresses the biggest misperception about Indigo in this Channel9 video.

Bottom line: Microsoft is not taking MSMQ, COM+ or Remoting out of the platform; it’s just that Indigo, which subsumes the features of these other technologies, will do it all better.

Daniel Lehenbauer, an SDE on the Avalon team, has started a wiki providing helpful hints on using XAML as your new 3D file format and has provided a utility to help those playing with 3D in the WinHEC build of Longhorn (build 4074).

Jon Udell, a writer for InfoWorld, begins a series digging into the value proposition of Longhorn with a look at WinFS. Jeremy Mazner, a Microsoft evangelist focusing on WinFS, provides a counter-point.

Just to be clear, Marc Clifton’s MyXaml framework for adding a declarative UI mark-up language to today’s .NET framework is not a clone/sub-set of Microsoft’s XAML or Avalon targeted at Longhorn. In other words, while MyXaml provides a number of the benefits of declarative UI mark-up for building smart/rich clients today, MyXaml is not a way to write WinForms code today that will seamlessly turn into Avalon code tomorrow.

The reason I mention this is because I’ve seen some folks get a bit confused by the use of “Xaml” in the name (Marc is using XAML as the generic Extensible Application Mark-up Language and not as related to Microsoft’s XAML).

On the other hand, there are two other projects that are aiming to clone/sub-set XAML/Avalon on .NET today: Xamlon and Mobiform’s XAML products. I can’t claim that either of these will actually help you transition to Longhorn when it comes along, but I know that Xamlon’s XAML samples work with minor tweaks on their parser and on the WinHEC build of Longhorn.