v7.1.3

Fix InMemoryMessageBusChannel

Messages that are published while awaiting previous ones, will be awaited as well.
This makes sure there are no queued messages left in the channel.

v7.1.1

Improve InMemoryMessageBus to add capabillities for multi application scenarios.

v7.0.6

SequenceIdGenerator added

v7.0.5

fix sequence injection, added a simple sequence id generator

Hotfix 7.0.4

Hotfix/7.0.4 (#110)

* db conn aclaration

* exception logging & builder

* docs

* wait for data generation

* currentHolder with initial ctor

* xmldocs

* wait for default tenant

* xmldocs

* formatting

* logging improved

* xmldocs

* xmldocs

* method detection standardized

* xmldocs

* method detections

* xmldocs

* description and min version

* fix logging of errors array

* cherrypick-errors fixed

* dependency fix

* test fix

* correlation holder is injected, must not contain more public ctors

* build triggers adapted

* master -> main

7.0.0

Release/7.0.0 (#103)

* Refactor: Invokers

* test coverage & fixes

* code cleanup r#
db Application as decorator
tenant default culture removed

* test coverage

* integration fixes

* message bus invocation sequentialized, waiting for app boot

* logging

* compile fix

* no exception logging or handling in invoker

* typo

* flexible MessageName vs. Event Type
Messagebus.Connect on boot

* test fixes

* test logging

* test ignored on CI pipeline

* exception handling

* Serilog Implementation

* auto registration of integration message handlers

* removed call to obsolete logger func

* sourcelink, absolete calls in tests

* Create Logger by string category tries to derive a type

* EF Core 5.0

* JetBrains.Annotations bumped

* logging bumps

v7.0.0-beta.2+14

Invoke now allows configuration of scope before invoking the action; …

v7.0.0-beta.1+5

Invoke now allows configuration of scope before invoking the action; …

v6.2.3+1

Invoke now allows configuration of scope before invoking the action; …

v6.2.2+1

Feature/correlations (#100)

* new Correlation type with unique id per scope
* correlation id gets automatically published in integration events
* optional correlation for events outside of scopes (tenant creation)