v1.1.1

Bug Fixes

• If an event handler changed a previously unchanged entity, it could result in an exception due to the change tracker enumerable changing

v1.1.0

1.1.0

API Changes

All events (OnInserting, OnInserted, etc...) have been updated to accept the EntityEntry rather than the entity object itself in order to allow event handlers to take advantage of any metadata they might need. The overloads accepting the object entity has been marked obsolete and will be removed in future versions.

New Features

Audit Tracking now provides better support for owned types. Previously, in order to track owned types, each owned type needed to implement the ITrack<Event>Date interfaces themselves. This caused an awkward database schema, since most owned types get stored into the same table row. From a database row perspective, the most convenient way to track changes to track any column change as an update to the whole row. So now, updates to owned types will update the UpdateDate property (if it exists) on the owning record. If the owned type implements the tracking interfaces themselves, the owning record will be left alone. In other words, the most specific record in the ownership chain will be updated.

v1.0.1

Initial Release

Provides a simple, dependency-injection based mechanism for easily adding event based behaviors such as auditing to your data models. Supports the following events

• Inserting
• Inserted
• Updating
• Updated
• Deleting
• Deleted