docs/content/about/release-notes.md
Features:
Bug Fixed:
What's Changed:
Bug Fixed:
Features:
Breaking Changes
Removed DefaultAuthenticationScheme, UseChallengeOnAuth, DefaultChallengeScheme and AuthorizationPolicy options of DotNetCore.CAP.Dashboard.
Now CAP dashboard auth/authz mechanism to leverage the "ASP.NET Core" way of doing it, see #1428.
Features:
FallbackWindowLookbackSeconds option to configure the retry processor to pick up the backtrack time window for Scheduled or Failed status messages. (#1455) Thanks @apatoziBug Fixed:
Features:
Bug Fixed:
Features:
EnableConsumerPrefetch and UseDispatchingPerGroup will work together without interference. (#1399)Bug Fixed:
Breaking Changes
ProducerThreadCount configuration option. Now automatically send task managed by the .NET thread pool. (#1380)Features:
Bug Fixed:
Features:
AutoDeleteOnIdle option for Azure Service Bus. (#1350) Thanks @StevenDevooghtBug Fixed:
FailedRetryInterval. (#1359) Thanks @li-zheng-haoUseDispatchingPerGroup option. (#1356) Thanks @sampsonye @li-zheng-haoFeatures:
Bug Fixed:
Bug Fixed:
Features:
Bug Fixed:
Features:
Bug Fixed:
Features:
Bug Fixed:
Features:
Bug Fixed:
Bug Fixed:
Breaking Changes:
SubscribeFilter method to asynchronous.IConsumerClient interface OnMessage and OnLog is from event to delegate.Features:
Others:
Bug Fixed:
Bug Fixed:
Features:
Bug Fixed:
Features:
Bug Fixed:
Bug Fixed:
Features:
Features:
Bug Fixed:
Bug Fixed:
Features:
Bug Fixed:
Features:
Bug Fixed:
Bug Fixed:
Features:
Bug Fixed:
Features:
Bug Fixed:
Features:
Bug Fixed:
Features:
Bug Fixed:
Features:
Bug Fixed:
Features:
Bug Fixed:
Bug Fixed:
Bug Fixed:
Bug Fixed:
Bug Fixed:
Breaking Changes:
In this version, we have made major improvements to the code structure, which have introduced some destructive changes.
Publisher and Consumer are not compatible with older versions This version is not compatible with older versions of the message protocol because we have improved the format in which messages are published and stored.
Interface changes We have done a lot of refactoring of the code, and some of the interfaces may be incompatible with older versions
Detach the dashboard project
Features:
ISerializer to support serialization of message body sent to MQ.ICapPublisher to publish message with headers.Bug Fixed:
Features:
ConsumerInvoker implementation. Thanks @hetaoosBug Fixed:
Features:
Bugs Fixed:
Features:
Bug Fixed:
Features:
Bug Fixed:
Bug Fixed:
Features:
Breaking Changes:
In order to support the "version isolation" feature, we introduced a new version field in version 2.4.0 to isolate different versions of the message, so this requires some adjustments to the database table structure. You can use the following SQL to add a version field to your database CAP related table.
MySQL
ALTER TABLE `cap.published` ADD Version VARCHAR(20) NULL;
ALTER TABLE `cap.received` ADD Version VARCHAR(20) NULL;
SQL Server
ALTER TABLE Cap.[Published] ADD Version VARCHAR(20) NULL;
ALTER TABLE Cap.[Received] ADD Version VARCHAR(20) NULL;
PostgreSQL
ALTER TABLE cap.published ADD "Version" VARCHAR(20) NULL;
ALTER TABLE cap.received ADD "Version" VARCHAR(20) NULL;
MongoDb
db.CapPublishedMessage.update({},{"$set" : {"Version" : "1"}});
db.CapReceivedMessage.update({},{"$set" : {"Version" : "1"}});
Bug Fixed:
Features:
Bug Fixed:
In this version, we made some breaking changes for the publisher API, you can see this blog to understand the story behind.
If you have any migration question, please comment in issue (#190).
Breaking Changes:
Features:
Bug Fixed:
Features:
Bug Fixed:
Because version 2.2.3 was not released to nuget, so released 2.2.4.
Features:
Bug Fixed:
Features:
Bug Fixed:
Bug Fixed:
Features:
Bug Fixed:
Features:
Bug Fixed:
Features:
Bug Fixed:
Bug Fixed:
Bug Fixed:
Features:
Bug Fixed:
Bug Fixed:
Bug Fixed:
Features:
ICapPublisher api supported callback subsrciber.Bug Fixed:
Features:
ICapPublisher.Bug Fixed:
Features: