As applications age, one of the challenges is often how to access it in a way that’s consistent with the rest of your code assets. You can expand access while still retaining the original surface area for existing apps. One way to do that is to generate a wrapping layer based on the APIs. One benefit of this approach is consistency across multiple wrapped APIs, whether via web API, CLI, messaging, or an alternate library. This talk explores where this might be appropriate and likely design challenges. You’ll also see implementation oof a medium complexity API. Along the way you’ll learn a bit about System.CommandLine and Roslyn source generation.

This is a 60-75 minute talk