4.0.0-preview2
Pre-release
Pre-release
rossgrambo
released this
28 Mar 23:14
·
140 commits
to release/v4
since this release
Microsoft.FeatureManagement Updates
The packages associated with this release are
- Microsoft.FeatureManagement 4.0.0-preview2
- Microsoft.FeatureManagement.AspNetCore 4.0.0-preview2
- Microsoft.FeatureManagement.Telemetry.ApplicationInsights 4.0.0-preview2
- Microsoft.FeatureManagement.Telemetry.ApplicationInsights.AspNetCore 4.0.0-preview2
Microsoft.FeatureManagement
Enhancements
- Added support for variant feature flag-based service provider in dependency injection. It allows different service implementations to be injected automatically for different targeted audiences based on their variant assignment. (#39). See more details here.
- Added a
TargetingContext
property to theEvaluationEvent
. This allows feature evaluation events to accurately represent what the targeting context was at the time of feature evaluation. (#409)
Microsoft.FeatureManagement.AspNetCore
Enhancements
- Introduced a new ASP.NET Core middleware called
TargetingHttpContextMiddleware
. It makes targeting information available fromHttpContext
on each request. (#409) - Added support for .NET 8 target framework. (#364)
Microsoft.FeatureManagement.Telemetry.ApplicationInsights
Enhancements
- Added a
TargetingId
property to the feature evaluation events sent to Application Insights. TheTargetingId
is the identifier of a targeted user during feature evaluation. This new property allows you to correlate feature evaluation events with other telemetry data your application sends to Application Insights, as long as they share the sameTargetingId
. (#409)
Microsoft.FeatureManagement.Telemetry.ApplicationInsights.AspNetCore
Enhancements
- Introduced a telemetry initializer named
TargetingTelemetryInitializer
. It automatically adds targeting information to telemetry data your application sends to Application Insights. This can be used to correlate your telemetry data with feature evaluation events based on the targeting information during your telemetry analysis. (#409)