Thanks to everyone who attended the Boise Launch for Visual Studio.NET 2003/Windows Server 2003.  I've posted the slides on this site, so here's the link to last weeks Seattle Launch.  You'll find all the code and slides there, as well as mentions of all the tools I used in the decks.

For those of you who dug my original .NET Zen Koans here are the new ones:

I'm twenty nine years
And always sought the
Way of the
Framework.
Well, this morning we passed
Like strangers on the road.

Whenever a object is created,
Be aware of it,
As soon as you are
aware of it,
It will vanish.
If you remain for a
long period
Forgetful of objects,
You will naturally become unified like the .NET Framework.
This is the essential art of Computer Zen.

People think it is hard to see .NET,
but in reality
it is neither difficult nor easy.
It is a matter of responding
to C# and VB.NET while remaining detached
from the runtime,
living in the midst of managed code yet being detached from managed code, seeing without seeing, hearing without hearing, garbage collecting without garbage collecting.

One minute of sitting,
one inch of Buddha,
one line of code.
Like lightning all thoughts come and pass.
Just once look
into your mind-depths:
Now look it up on MSDN.

However deep your
knowledge of the .NET Framework,
it is no more
than a strand of hair in the vastness of space.
However important seeming your object model,
it is but a drop of water in a deep ravine.

How profoundly silent is the .NET Framework!
Boundless and infinite,
it is the dwelling place
of the divine.
Rich classes with properties and methods are flourishing and spreading.
Forgetful of words I roam and rest here.

Jon is blogging the CTO Forum.  He includes a great summary of Adam Bosworth's talk, but a few concepts/quotes from Bosworth stood out to me.

Public contracts. You can change your operating system, you can change your object model, but don't change your public contract. We know this works. "The proof point is the web."

Message-driven model. We need a programming model for message-driven programming. How does a developer write code in that environment? "It's no problem for systems programmers, but for everybody else, it's a challenge to make it easy for them to write apps that wake up when a message comes in."

The more I think about information architecture, specifically web services public interfaces (currently in the concrete form of WSDL, but mostly in my head) the more I grok the importance and usefulness of immutable public contracts.  Which gets me thinking about the tribulations involved in versioning...I certainly don't want to get the habit of names like SonOfWebServiceEx2.  This has led me to Yasser (don't all things like to Yasser? :) ) and his article that touches on the subject, as well as Scott Seely's article on evolving an interface.  I haven't yet decided if I agree with Matt Powell's belief that XmlElement can make life that much better...he agrees that it doesn't promise to make it easier.