I spent a week in Redmond in January taking part in a focus group on the vision for the P&P's new Prism work on composite applications. Part of the week long exercise was to identify the basic building blocks of building large composite clients. This is my list of the significant parts of an...

EDIT: Oops on my part. This is effectively the Active Object pattern. The rest of the Build your own CAB series can be found at the table of contents . There's a thread on the altdotnet list this morning about how to unit test background operations originating from a screen Presenter . I have a strategy...

Rob Kitson has put together a set of code examples that demonstrate the screen patterns mentioned in the BYOC series . Read more about it at Keeping UI construction DRY . Thanks Rob!

Yesterday I was part of a lot of conversations about building composite desktop applications. The people in attendance are building a myriad array of large desktop clients and they're facing some substantial challenges. Offhand, I remember hearing: The desire to reuse business logic between user...

The other umpteen parts of the series are here in the Table of Contents . A large part of building a composite application is "wiring" the pieces together. You're wiring views to presenters, commands to menus, and security rules to elements of the screen. Since you're trying to make...

There's been a bit of chatter today on the altdotnet list about whether to use the CAB, another framework, or roll your own . It seemed like a good time to get off my duff and start writing some new installments in the Build your own CAB series. When I wrote an earlier installment on the Event Aggregator...

There's yet another (worthy) discussion going on in the altdotnet list about whether or not to choose CAB, another framework, or roll your own framework for a given desktop client (I'm saying desktop client here because I'm thinking of the superset of either WinForms or WPF regardless if...

After a bit of a hiatus and a fair amount of pestering, I'm back and ready to continue the "Build you own CAB" series . The point isn't really to go build a drop in replacement for the Composite Application Block (CAB), but rather to understand the design patterns you can use to build...

The entire content is now online as a page on my site at: Build your own CAB #14: Managing Menu State with MicroController's, Command's, a Layer SuperType, some StructureMap Pixie Dust, and a Dollop of Fluent Interface Community Server really, really didn't like this post and just wouldn't...

The title is a mouthful and accurately implies an alarmingly high jargon to code ration, but I just didn't see anyway to write this post without straying into all of these different subjects. When you try to write an explanatory article you have to walk a tightrope between a sample problem that's...