You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 22, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,10 @@
2
2
3
3
All notable changes to the LaunchDarkly .NET SDK Redis integration will be documented in this file. This project adheres to [Semantic Versioning](http://semver.org).
4
4
5
+
## [1.1.1] - 2019-05-13
6
+
### Changed:
7
+
- Corresponding to the SDK package name change from `LaunchDarkly.Client` to `LaunchDarkly.ServerSdk`, this package is now called `LaunchDarkly.ServerSdk.Redis` (or `LaunchDarkly.ServerSdk.Redis.StrongName`). The functionality of the package, including the namespaces and class names, has not changed.
8
+
5
9
## [1.1.0] - 2019-01-14
6
10
### Added
7
11
-`RedisFeatureStoreBuilder.WithCaching` is the new way to configure local caching behavior, using the new SDK class `FeatureStoreCacheConfig`. This allows you to specify a limit on the number of cached items, which was not previously possible. Future releases of the SDK may add more caching parameters, which will then be automatically supported by this library.
This library provides a Redis-backed persistence mechanism (feature store) for the [LaunchDarkly .NET SDK](https://github.com/launchdarkly/dotnet-client), replacing the default in-memory feature store. The underlying Redis client implementation is [StackExchange.Redis](https://github.com/StackExchange/StackExchange.Redis).
5
+
This library provides a Redis-backed persistence mechanism (feature store) for the [LaunchDarkly .NET SDK](https://github.com/launchdarkly/dotnet-server-sdk), replacing the default in-memory feature store. The underlying Redis client implementation is [StackExchange.Redis](https://github.com/StackExchange/StackExchange.Redis).
6
6
7
7
The minimum version of the LaunchDarkly .NET SDK for use with this library is 5.6.1.
8
8
9
9
For more information, see also: [Using a persistent feature store](https://docs.launchdarkly.com/v2.0/docs/using-a-persistent-feature-store).
10
10
11
-
.NET platform compatibility
12
-
---------------------------
11
+
## .NET platform compatibility
13
12
14
13
This version of the library is compatible with .NET Framework version 4.5 and above, .NET Standard 1.6, and .NET Standard 2.0.
15
14
16
-
Quick setup
17
-
-----------
15
+
## Quick setup
18
16
19
17
1. Use [NuGet](http://docs.nuget.org/docs/start-here/using-the-package-manager-console) to add this package to your project:
20
18
21
-
Install-Package LaunchDarkly.Client.Redis
19
+
Install-Package LaunchDarkly.ServerSdk.Redis
22
20
23
21
Or, if you require a strong-named assembly (note that this will result in a transitive dependency on StackExchange.Redis.StrongName, rather than StackExchange.Redis):
2. Import the package (note that the namespace is different from the package name):
28
26
29
27
using LaunchDarkly.Client.Redis;
30
28
@@ -51,8 +49,7 @@ Quick setup
51
49
.WithUseLdd(true);
52
50
LdClient ldClient = new LdClient(ldConfig);
53
51
54
-
Caching behavior
55
-
----------------
52
+
## Caching behavior
56
53
57
54
To reduce traffic to the Redis server, there is an optional in-memory cache that retains the last known data for a configurable amount of time. This is on by default; to turn it off (and guarantee that the latest feature flag data will always be retrieved from Redis for every flag evaluation), configure the builder as follows:
58
55
@@ -64,47 +61,33 @@ Or, to cache for longer than the default of 30 seconds:
The published versions of these assemblies are digitally signed by LaunchDarkly.
71
67
72
-
The `LaunchDarkly.Client.Redis.StrongName` assembly is also [strong-named](https://docs.microsoft.com/en-us/dotnet/framework/app-domains/strong-named-assemblies); `LaunchDarkly.Client.Redis` is not strong-named. The reason for this difference is that the StackExchange.Redis library is also built in two versions so if LaunchDarkly provided only a strong-named version, it would cause a dependency conflict if the application happened to be using the non-strong-named version of StackExchange.Redis for other purposes.
68
+
The `LaunchDarkly.ServerSdk.Redis.StrongName` assembly is also [strong-named](https://docs.microsoft.com/en-us/dotnet/framework/app-domains/strong-named-assemblies); `LaunchDarkly.ServerSdk.Redis` is not strong-named. The reason for this difference is that the StackExchange.Redis library is also built in two versions so if LaunchDarkly provided only a strong-named version, it would cause a dependency conflict if the application happened to be using the non-strong-named version of StackExchange.Redis for other purposes.
73
69
74
70
Building the code locally in the default Debug configuration does not sign the assembly and does not require a key file.
75
71
76
-
Development notes
77
-
-----------------
72
+
## Development notes
78
73
79
-
This project imports the `dotnet-base` and `dotnet-client-shared-tests` repositories as subtrees. See the `README.md` file in each of those directories for more information.
74
+
This project imports the `dotnet-base` and `dotnet-server-sdk-shared-tests` repositories as subtrees. See the `README.md` file in each of those directories for more information.
80
75
81
76
To run unit tests, you must have a local Redis server.
82
77
83
78
Releases are done using the release script in `dotnet-base`. Since the published package includes a .NET Framework 4.5 build, the release must be done from Windows.
84
79
85
-
About LaunchDarkly
86
-
-----------
87
-
80
+
## About LaunchDarkly
81
+
88
82
* LaunchDarkly is a continuous delivery platform that provides feature flags as a service and allows developers to iterate quickly and safely. We allow you to easily flag your features and manage them from the LaunchDarkly dashboard. With LaunchDarkly, you can:
89
83
* Roll out a new feature to a subset of your users (like a group of users who opt-in to a beta tester group), gathering feedback and bug reports from real-world use cases.
90
84
* Gradually roll out a feature to an increasing percentage of users, and track the effect that the feature has on key metrics (for instance, how likely is a user to complete a purchase if they have feature A versus feature B?).
91
85
* Turn off a feature that you realize is causing performance problems in production, without needing to re-deploy, or even restart the application with a changed configuration file.
92
86
* Grant access to certain features based on user attributes, like payment plan (eg: users on the ‘gold’ plan get access to more features than users in the ‘silver’ plan). Disable parts of your application to facilitate maintenance, without taking everything offline.
* LaunchDarkly provides feature flag SDKs for a wide variety of languages and technologies. Check out [our documentation](https://docs.launchdarkly.com/docs) for a complete list.
105
88
* Explore LaunchDarkly
106
-
*[launchdarkly.com](http://www.launchdarkly.com/"LaunchDarkly Main Website") for more information
107
-
*[docs.launchdarkly.com](http://docs.launchdarkly.com/"LaunchDarkly Documentation") for our documentation and SDKs
108
-
*[apidocs.launchdarkly.com](http://apidocs.launchdarkly.com/"LaunchDarkly API Documentation") for our API documentation
109
-
*[blog.launchdarkly.com](http://blog.launchdarkly.com/"LaunchDarkly Blog Documentation") for the latest product updates
89
+
*[launchdarkly.com](https://www.launchdarkly.com/"LaunchDarkly Main Website") for more information
90
+
*[docs.launchdarkly.com](https://docs.launchdarkly.com/"LaunchDarkly Documentation") for our documentation and SDK reference guides
91
+
*[apidocs.launchdarkly.com](https://apidocs.launchdarkly.com/"LaunchDarkly API Documentation") for our API documentation
92
+
*[blog.launchdarkly.com](https://blog.launchdarkly.com/"LaunchDarkly Blog Documentation") for the latest product updates
110
93
*[Feature Flagging Guide](https://github.com/launchdarkly/featureflags/"Feature Flagging Guide") for best practices and strategies
0 commit comments