This repository has been archived by the owner on Oct 30, 2024. It is now read-only.
Releases: launchdarkly/dotnet-server-sdk
Releases · launchdarkly/dotnet-server-sdk
4.0.0
[4.0.0] - 2018-02-21
Added
- Support for a new LaunchDarkly feature: reusable user segments.
Changed
- The client now uses Common.Logging.
- The
FeatureStore
interface has been changed to support user segment data as well as feature flags. Existing code that usesInMemoryFeatureStore
orRedisFeatureStore
should work as before, but custom feature store implementations will need to be updated. - Some previously public classes that were not meant to be public are now internal.
Fixed
- All previously undocumented methods now have documentation comments.
Removed
- Obsolete/deprecated methods have been removed.
- Removed
Configuration.WithLoggerFactory
since the logging framework has changed. For more details on setting up logging, see here.
3.6.1
[3.6.1] - 2018-02-21
Fixed
- Improved performance of the semantic version operators by precompiling a regex.
3.6.0
[3.6.0] - 2018-02-19
Added
- New property
LdClient.Version
returns the client's current version number. - Adds support for a future LaunchDarkly feature, coming soon: semantic version user attributes.
- Custom attributes can now have long integer values.
3.5.0
[3.5.0] - 2018-01-29
Added
- Support for specifying private user attributes in order to prevent user attributes from being sent in analytics events back to LaunchDarkly. See the
AllAttributesPrivate
andPrivateAttributeNames
methods onConfiguration
as well as theAndPrivateX
methods onUser
.
Changed
- The stream connection will now restart when a large feature flag update fails repeatedly to ensure that the client is using most recent flag values.
- Client no longer reconnects after detecting an invalidated SDK key.
3.4.1
[3.4.1]
Added
- Framework target for netstandard1.4 and netstandard2.0. Thanks @nolanblew and @ISkomorokh!
- Added the Apache 2.0 license to
LaunchDarkly.Client.csproj
Changed
- Fixed a bug causing ASP.NET applications to be blocked during client initialization.
- Removed unused and transitive dependencies.
- Improved logging. Thanks @MorganVergara and @JeffAshton!
3.4.0
[3.4.0] - 2017-11-29
Added
- 🚀 Support for Streaming via Server-Sent Events as an alternative to Polling. HTTP-based streaming is favored over polling to reduce network traffic and propagate feature flag updates faster. 🚀
- New builder parameters to complement streaming functionality
WithIsStreamingEnabled
: Set whether streaming mode should be enabled,true
by default.WithStreamUri
: Set the base URL of the LaunchDarkly streaming server. May be used in conjunction with the LaunchDarkly Relay Proxy.WithReadTimeout
: The timeout when reading data from the streaming API. Defaults to 5 minutesWithReconnectTime
: The time to wait before attempting to reconnect to the streaming API. Defaults to 1 second
- Apache 2.0 License
Changed
- Streaming is now used to retrieve feature flag configurations by default.
- Minimum (and default) polling interval changed from 1 second to 30 seconds.
PollingProcessor
no longer retries failed feature flag polling attempts.
3.3.2
[3.3.2] - 2017-08-30
Changed
- Updated dependency versions. Thanks @ISkomorokh!
- Exceptions in
FeatureRequestor
are rethrown without replacing stack information
3.3.1
3.3.0
[3.3.0] - 2017-06-16
Added
- Config option to use custom implementation of IFeatureStore
- Artifact is now signed
Changed
- Removed NETStandard.Library from dependencies so it isn't brought in by non-.NET core projects.
- Project files migrated to current
*.csproj
standard - Fixed release that inadvertently removed the ability to set a custom HttpClientHandler
3.2.0
[3.2.0] - 2017-05-25
Added
- Config option to use custom implementation of IFeatureStore
- Artifact is now signed
Changed
- Removed NETStandard.Library from dependencies so it isn't brought in by non-.NET core projects.
- Project files migrated to current
*.csproj
standard