CAP | C# Ecosystem Directory

Bot releases are visible (Hide)

CAP - 3.0.0

Published by yang-xiaodong almost 5 years ago

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:

Supports .NET Core 3.1.
Upgrade dependent packages.
New serialization interface ISerializer to support serialization of message body sent to MQ.
Add new api for ICapPublisher to publish message with headers.
Diagnostics event structure and names improved. #378
Support consumer method to read the message headers. #472
Support rename message storage tables. #435
Support for Kafka to write such as Offset and Partition to the header. #374
Improved the processor retry interval time. #444

Bug Fixed:

Fixed SqlServer dashboard sql query bug. #470
Fixed Kafka health check bug. #436
Fixed dashboard bugs. #412 #404
Fixed transaction bug for sql server when using EF. #402

CAP - 2.6.0

Published by yang-xiaodong about 5 years ago

Features:

Improvement Diagnostic support. Thanks @gfx687
Improvement documention. https://cap.dotnetcore.xyz
Improvement ConsumerInvoker implementation. Thanks @hetaoos
Support multiple consumer threads. (#295)
Change DashboardMiddleware to async. (#390) Thanks @liuzhenyulive

Bug Fixed:

SQL Server Options Bug.
Fix transaction scope disposed bug. (#365)
Fix thread safe issue of ICapPublisher bug. (#371)
Improved Ctrl+C action raised exception issue.
Fixed asynchronous exception catching bug of sending.
Fix MatchPoundUsingRegex "." not escaped bug (#373)

CAP - 2.5.1

Published by yang-xiaodong over 5 years ago

Features:

Improved logs record.
Upgrade dependent nuget packages version. (MySqlConnector, confluent-kafka-dotnet-1.0 )
NodeId type change to string of DiscoveryOptions for Consul. (#314)
Change the IConsumerServiceSelector interface access modifier to public. (#333)
Improved RabbitMQOptions to provide extensions option to configure the client original configuration. (#350)
Add index for MongoDB CAP collections. (#353)

Bugs Fixed:

Fixed consumer re-register transport bug. (#329)
Handle messages retrieval failure. (#324)
Fixed DiagnosticListener null reference exception bug. (#335)
Add subscription name validation for the AzureServerBus. (#344)
Fixed thread safety issues of publisher. (#331)

CAP - 2.5.0

Published by yang-xiaodong over 5 years ago

Features:

Support Azure Service Bus. #307
Support In-Memory Storage. #296
Upgrade Dapper to version 1.60.1
Support read environment variables CAP_WORKERID and CAP_DATACENTERID as the snowflake algorithm workerid and datacenterid.

Bug Fixed:

Modify MySQL cap table encoding to utf8mb4. #305
Move CapSubscribeAttribute class to DotNetCore.CAP project.
Fixed multiple instance snowflake algorithm generating primary key conflicts. #294

CAP - 2.4.2

Published by yang-xiaodong almost 6 years ago

Features:

Startup the CAP with the .NET Core 2.1 BackgroundService. #265
Improved message delivery performance. #261

Bug Fixed:

Fixed PostgreSql version isolation feature bug. #256
Fixed SQL Server sql bug for dashboard search. #266

CAP - 2.4.1

Published by yang-xiaodong almost 6 years ago

Bug Fixed:

Fixed MongoDB version isolation feature bug. (#253)

CAP - 2.4.0

Published by yang-xiaodong almost 6 years ago

Features :

Supported version options. (#220)
Upgrade nuget package to .net core 2.2.

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:

Fixed different groups of the same topic name in one instance will cause routing bug. (#235)
Fixed message presistence bug. (#240)
Fixed RabbitMQ topic name contains numbers will cause exception bug. (#181)

CAP - 2.3.1

Published by yang-xiaodong almost 6 years ago

Features:

Add Source Link Support
Upgrade dependent NuGet packages.

Bug Fixed:

Fixed dashboard messages requeue error. ( #205 )
Adjustment snowflake workerId to random id.
Fixed flush unclaer data bug.

CAP - 2.3.0

Published by yang-xiaodong about 6 years ago

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:

Removed app.UseCap() from Startup.cs
Message table primary key data type has been modified to Bigint and non auto-Increment. (#180)
New publisher Api. (#188)

Features:

MongoDb supported. (#143)
Automatic commit transaction. (#191)