One of the first major deliverables produced by the patterns & practices team is Application Architecture for .NET: Designing Applications and Services. This guide is now getting close to 5 years old (it was written by Ed long before I joined the team), but unlike some of our other early deliverables, we've found that it's still surprisingly popular for its age. This is probably partly due the fact that the guide is written at a sufficiently high level for it to still be relevant despite the changes and advances to the platform.
Even so, we've decided that this guide is now due for a refresh, and we'd like your help in figuring out which direction we should take it. In addition to the changes in the underlying platform and in the industry's understanding of architecture, the patterns & practices portfolio has evolved significantly, and we want to be thoughtful on what type of content should go into an updated Application Architecture guide and what content should go in other places such as software factories or Enterprise Library.
Feel free to send us any weird and wonderful ideas you have for the next version of the guide, but to get you thinking, here are a few questions that are on my mind:
I'm quite excited about finally updating this guide, and we're looking forward to your perspectives on what it should be.
Buenas, uno de las primeras guías de lectura obligada de la gente de Microsoft Patterns and Practices
Those of you who have been paying attention may have remembered a post I did over a year ago announcing
W marcu zeszłego roku Tom Hollander pochwalił się, że wspólnie z kolegami z Patterns&Practices