After the auspicious success that the original Application Architecture Guidance (version 1.0) had had, there was a series of books on fine tuning aspects such as security, performance, scalability, smart client internals, web applications and so on
But all that happened between 2002 and 2004 during the timeframe of .NET 1.0 and 1.1. And part of the gotten feedback was later used during the maturation stages of .NET 2.0 however...
While best practices were departing from the architect agenda to land inherently into the development platform (something known as commoditization phase), architects started staying with a bitter taste in their throats. Had Architecture, in capitals, dead?
That question emerged time and time again
Until finally PnP Architect J.D. Meier took the lead and turned the engine back on with his now legendary post "patterns & practices App Arch Guide 2.0 Project". J.D. started apologizing in some way: "It's long overdo..."
I was taking a quick look (as I find the time for, I'm also contributor for this project), I can guarantee the reader that this is not just a book migration from .NET 1.0/1.1 to .NET 3.5 SP1 but a complete redefinition of what Application Architecture means today. Even beyond the .NET platform, why not
This important point could be confirmed just by checking how the information is organized along the book
Application types, Architecture styles, cross-cutting concerns and an overall frame of features that every architecture must take into account (no matter the application type being supported or the style being followed as blueprint)
J.D. encourages the reader to download and apply these resources as already finished guidance, in order to provide feedback through the Codeplex discussion engine (see "Discussions" and "Issue Tracker" tabs), or by telling your experiences turning over the match by using this guidance to MyStory@Microsoft.com
It's just the Beta 1 but it's really taking shape. Be part of the project and help J.D. make worth the wait!