We’re excited to announce that Harness Feature Flags now officially supports our open source .NET SDK. Users can now leverage .NET in their server-side applications and services for all of their feature flag needs. They can implement software switches to hide or activate features and avoid a painful rollback meaning using .NET has just gotten easier.
.NET has been a staple of the web and desktop development communities for many years, originally starting with support for Windows but having since expanded the framework to support Linux and MacOS as well. With how ubiquitous it is, especially for large enterprises and even many newer organizations, providing first-class support for .NET in Harness Feature Flags became a must-have.
It’s important to note that users can expect the same feature support and performance that they’re used to from other open source Harness Feature Flag SDKs. If you’re already familiar with any of the other SDKs supported, the same patterns and use cases apply.
To start using .NET for your own feature flags, check out the .NET SDK Reference. This will walk you through how to get a hold of the SDK, how to initialize, and of course, how to create your first feature flag.
Using the .NET SDK is only half the equation. While it’s critical to ensure the SDK is working as expected, wrapping your features or changes in a flag inside your codebase is one of two things you need to do to have a fully functional feature flag.
If you haven't already, you'll want to head over to your Harness project and create a flag in the app itself. Once both pieces are done, you’ll be ready to roll out your feature flag. If you need additional help, you can either follow the in-app wizard, or you can check out the Getting Started documentation.
Enjoyed reading this blog post or have questions or feedback?
Share your thoughts by creating a new topic in the Harness community forum.