Feature Flags in .NET 8: ASP.NET Core, Minimal APIs, Blazor
The article discusses the implementation of feature flags in .NET 8, particularly within ASP.NET Core and Blazor applications. Feature flags allow developers to separate code deployment from feature release, enabling gradual rollouts and quick rollbacks if issues arise. The article provides a quick start guide for integrating feature flags using the Rollgate SDK.
- ▪Feature flags help manage the deployment of new features without affecting all users at once.
- ▪Developers can monitor metrics and gradually increase user exposure to new features.
- ▪The article includes code examples for initializing the Rollgate SDK and implementing feature flags in ASP.NET Core.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 2672712) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Domenico Giordano Posted on May 24 • Originally published at rollgate.io Feature Flags in .NET 8: ASP.NET Core, Minimal APIs, Blazor #dotnet #csharp #aspnetcore #featureflags This post was originally published on rollgate.io/blog/feature-flags-aspnet-core. Every .NET team eventually hits the same wall: you have a feature ready in staging, but pushing it to production means flipping a switch for every user at once.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).