v2.0.0-rc2
- Know Issue
If you are using the ADO.NET provider for reminders, there is a bug in the configuration extension methodUseAdoNetReminderServicethat prevents it from working properly. The workaround is to explicitly configure the settings as in the following example:
.UseAdoNetReminderService((AdoNetReminderTableOptions options) => { })
.Configure<AdoNetReminderTableOptions>(options =>
{
options.ConnectionString = ConnectionString;
options.Invariant = "System.Data.SqlClient";
})-
Major changes (since 2.0.0-rc1)
- A new "facade" API for easier configuration of various aspects of stream providers: Persistent stream configurators (#4164)
-
Breaking changes
-
Non-breaking improvements
- Improve usability of dev cluster (#4090)
- Extensions should add their own application parts (#4091)
- Moved IStartupTask to Runtime.Abstractions package. Address #4106 (#4108)
- Improve configuration validators for ADO.NET configuration (#4097)
- In ActivationCountPlacementDirector, place locally if the cache is not populated yet (#4130)
- Improve usability of custom grain placement configuration (#4102)
- Remove legacy configuration requirement from Service Fabric hosting (#4138)
- Fix #4123: use List instead of IList in StaticGatewayListProviderOptions (#4147)
- Support treating all descendants of a base class as [Serializable] (#4133)
- Improve how grain services are registered (#4155)
- Do not call ResolveIPAddress in EndpointOptions constructor (#4171)
- When the silo shutdown, deactivate grain activations at an earlier stage (#4177)
- Improved transparancy and timing of silo lifecycle. (#4175)
- Set GrainService.Status to Started in the base implementation of StartInBackground(). (#4180)
- Validate that a ClusterId has been specified (#4160)
-
Non-breaking bug fixes