v3.0.0-beta.3

Fixed an issue where the DbContext was not correctly forwarded to trigger instances

v3.0.0-beta.2

Fixed release issue with beta.1

v3.0.0-beta.1

A first release that targets EF Core 6. This release is functionally in-line with v2.4.0-beta.1

v2.4.0-beta.1

Triggers are now able to attach state to an Entity through the newly added Items property exposed on the trigger context. This enables advanced scenarios such as preserving entity state between different lifecycles within a trigger and communication between triggers regarding a specific entity.

In addition, each trigger session is now configurable. (A trigger session automatically gets created and disposed of by default at the start and end respectively of a call to dbContext.SaveChanges()). This includes the ability to disable triggers altogether.

What's new:

• A newly added entity state management feature on TriggerContext.
• An extension method to get the current TriggerSession from a DbContext.
• An extension method allowing the creation and configuration of a TriggerSession
• Each trigger session can be configured with a custom MaxCascadeCycles property.
• Ability to Disable triggers within a session
• An extension method allowing the conditional creation of a new TriggerSession (or throws if one already exists).
• A set of extension methods (SaveChangesWithoutTriggers) that allow you to call SaveChanges() while disabling Triggers for that session

v2.3.2

• Fixed an issue with AddTriggeredDbContextFactory not using the provided factory type

v2.3.1

• Fixed an issue where using a DbContextFactory, a Trigger would not be able to get a hold on the DbContext that caused that trigger to be invoked
• added Readme as a nuget package artifact

v2.3.0

Trigger registration has been normalized in this release. Triggers that were registered with the DbContext would before be registered in and resolved from EF Cores internal service provider. This caused these triggers to not be able to participate with the application's DI container which was a severe limitation and required triggers to be registered with the applications DI container instead. This worked however as a result, all DbContexts that were used in the application would share the same triggers. This release resolves triggers registered with the DbContext through the applications DI container, it just works.

• BREAKING: Triggers that are registered with the DbContext will now instantiate instances using the applications DI container.
• New AddAsseblyTriggers extensions methods have been made available for TriggersContextOptionsBuilder

v1.4.0

Trigger registration has been normalized in this release. Triggers that were registered with the DbContext would before be registered in and resolved from EF Cores internal service provider. This caused these triggers to not be able to participate with the application's DI container which was a severe limitation and required triggers to be registered with the applications DI container instead. This worked however as a result, all DbContexts that were used in the application would share the same triggers. This release resolves triggers registered with the DbContext through the applications DI container, it just works.

• BREAKING: Triggers that are registered with the DbContext will now instantiate instances using the applications DI container.
• New AddAsseblyTriggers extensions methods have been made available for TriggersContextOptionsBuilder

v2.3.0-beta.2

• Trigger lifetimes are now properly respected
• Fewer allocations
• General performance improvements

v1.4.0-beta.2

• Trigger lifetimes are now properly respected
• Fewer allocations
• General performance improvements