Component-Based Capability Pattern: A Better Way to Handle Platform Differences
The Problem We Keep Running Into Building a system that talks to multiple platforms? You've probably written code like this: public class Platform { public string Name { get; set; } // Text stuff public bool SupportsText { get; set; } ...
