A proper v1 for EntityFrameworkCore.Projectables just got released! No longer do we need to struggle with untranslatable properties and methods https://t.co/cXbmfkzdrV
Today on the @dotnetdocsshow, @onthedrift2 will be talking to us about Scenario testing 🧪 Blazor Single-Page Apps
https://t.co/9tQiIFcdor #dotnet#blazor
@isaac_abraham@RogerAlsing@Razzee This means that any test within a scenario runs in isolation and can therefore manipulate the scenario to its likings without having to worry about affecting other tests that come after it
@isaac_abraham@RogerAlsing@Razzee Not exactly, A test within a scenario would play that Scenario up to where the test is actually taking place. IOW: all tests within a scenario will 'replay' the scenario and only execute that test. Typically many tests share a common scenario while only performing 'its' test
Take control of your DbContext!
Join the #EntityFramework#EFCore team with guest @onthedrift2 to discuss his EFCore.Triggered project that allows developers to respond to changes in their DbContext before and after they are committed to the database. 📽️ https://t.co/61fJRaUPfD
@melvinselvaraj Absolutely! I have a demo that does exactly that over here: https://t.co/7ehicGFGiA
Essentially any Entity that implements the IAudited interface will create an Audit record with the changes alongside saving the updated entity