3 posts tagged with "ASP.NET"

ASP.NET Core APIs often need to change behavior without requiring a new deployment. You might want to release functionality to a small group of users, make a feature available only to certain subscription tiers, or quickly disable a problematic change.

Feature flags make this possible by letting you change behavior remotely without modifying and redeploying your code.

In this tutorial, we'll build a simple ASP.NET Core Web API and use a ConfigCat feature flag to control if it returns a two-day or five-day weather forecast. Then, we'll add a targeting rule so only users on a premium subscription receive the full forecast.

A/B testing lets you compare two versions of a feature with real users and measure which one performs better. In an ASP.NET Core application, feature flags can handle which variation a user sees, while an analytics platform measures what happens afterward.

In this guide, we'll show you how to run an A/B test in ASP.NET Core using .NET 10, ConfigCat for experiment assignment, and Amplitude for analytics. We'll split users between two versions of an Add to Cart button and measure whether the change affects user behavior.

In this post, I'll investigate integrating ConfigCat's feature management system with an ASP.NET Core 8 Web API Service and the Options<T> pattern. We'll also leverage the built-in polling mechanism of the ConfigCat client library to refresh feature flags' states during the application's runtime. Let's get started!