.NET SDK reference (server-side)

Overview

This topic documents how to get started with the server-side .NET SDK, and links to reference information on all of the supported features.

Get started

After you complete the Getting Started process, follow these instructions to start using the LaunchDarkly SDK in your .NET application.

Install the SDK

First, install the LaunchDarkly SDK as a dependency in your application using your application's dependency manager.

Here's how:

Install-Package LaunchDarkly.ServerSdk
COPY

Next, import the LaunchDarkly SDK's namespaces in your application code. The namespace is not the same as the package name:

using LaunchDarkly.Sdk;
using LaunchDarkly.Sdk.Server;
// LaunchDarkly.Sdk defines general types like Context, which are also used in the client-side .NET SDK.
// LaunchDarkly.Sdk.Server defines the LdClient and Configuration types for the server-side .NET SDK.
COPY

Initialize the client

After you install and import the SDK, create a single, shared instance of LdClient. Specify your SDK key here to authorize your application to connect to a particular environment within LaunchDarkly.

To create a single instance:

LdClient client = new LdClient("sdk-key-123abc");
COPY

When you initialize the client, you can optionally provide configuration options. To learn how, read Configuration. To learn more about the specific configuration that are available in this SDK, read ConfigurationBuilder.

Evaluate a context

You can use client to check which variation a particular context will receive for a given feature flag. To learn more, read Evaluating flags and Flag evaluation reasons. For more information about how contexts are specified, read User and context configuration.

In the v7 example, the context key is the string "context-key-123abc". In the v6 example, the user key is the string "user-key-123abc":

var context = Context.Builder("context-key-123abc")
  .Name("Sandy")
  .Build();
var flagValue = client.BoolVariation(FeatureFlagKey, context, false);
if (flagValue) {
    // application code to show the feature
}
else {
    // the code to run if the feature is off
}
COPY

Contexts have a context kind of "user" by default. To specify a different kind, use the Kind method:

var context = Context.Builder("context-key-123abc")
  .Kind("device")
  .Name("Android")
  .Build();
COPY

To learn more, read Contexts and context kinds.

Transport Layer Security (TLS) and other networking issues

LaunchDarkly is deprecating support for TLS versions 1.0 and 1.1. .NET applications running on older operating systems are prone to use these older, less secure versions of TLS. It is possible to increase your application's security using AppContext switches.

To learn more, read Microsoft's documentation.

If you cannot update your application platform's configurations to support TLS version 1.2, you can update your application's SDK configuration to use new LaunchDarkly endpoints that support TLS versions 1.0 and later. Here is an example:

// Use `stream-tls10.launchdarkly.com` and `events-tls10.launchdarkly.com` TLSv1 endpoints
var config = Configuration.Builder("sdk-key-123abc")
    .DataSource(
        Components.StreamingDataSource()
            .BaseUri(new Uri("https://stream-tls10.launchdarkly.com")))
    .Events(
        Components.SendEvents()
            .BaseUri(new Uri("https://events-tls10.launchdarkly.com")))
    .Build();
COPY

Shut down the client

Shut down the client when your application terminates. To learn more, read Shutting down.

Supported features

This SDK supports the following features:

• Anonymous contexts and users
• Big segments
• Configuration, including
  • Application metadata configuration
  • Migration configuration
  • Service endpoint configuration
• Evaluating flags
• Flag evaluation reasons
• Flushing events
• Getting all flags
• Identifying and changing contexts
• Logging configuration
• Migrations
• Monitoring SDK status
• Offline mode
• OpenTelemetry
• Private attributes
• Reading flags from a file
• Relay Proxy configuration
  • Using proxy mode
  • Using daemon mode
• Secure mode
• Sending custom events
• Shutting down
• Storing data
• Subscribing to flag changes
• Test data sources
• User and context configuration
• Web proxy configuration