Getting Started with the .NET SDK

Split’s .NET SDK provides robust, scalable feature flag management in .NET, .NET Core and C#, giving any team the power to safely launch features and target them to users.

Why use Split for .NET?

Split’s .NET SDK brings scalable feature flagging to any app, website or experience built in the .NET framework. Split helps teams control rollouts, and customer experiences, while gathering new data and insight on how their products are being engaged. With Split, teams can:

  • Release features to production but disabled for all users by default
  • Target new features only to internal QA teams
  • Slowly roll out features to a broader audience by percentage, demographic, geography, account type, or any other metric
  • Kill features with a single click to revert back to your safe state

Split works across many different languages, letting developers, PMs and support teams control feature rollout from one unified view—and monitor the success of any new code. Our integrations bring rollout updates into the tools your team is already using, further opening the feature-delivery process up to your entire organization.

It provides you controlled rollout and feature toggles for C#, too.

Split gives developers working in C# unencumbered access to all the features of Split for .NET—they even use the same SDK.

Getting Started with Split for .NET

Split’s .NET SDK is very simple to integrate into your code base and is completely open source. All it really takes to get rolling with Split is initiating the SDK, then splitting your code.

View the Documentation