87fd4ad97d
* Upgrade to Duende.Identity * Linting * Get rid of last IdentityServer4 package * Fix identity test since Duende returns additional configuration * Use Configure PostConfigure is ran after ASP.NET's PostConfigure so ConfigurationManager was already configured and our HttpHandler wasn't being respected. * Regenerate lockfiles * Move to 6.0.4 for patches * fixes with testing * Add additional grant type supported in 6.0.4 and beautify * Lockfile refresh * Reapply lockfiles * Apply change to new WebAuthn logic * When automated merging fails me --------- Co-authored-by: Justin Baur <19896123+justindbaur@users.noreply.github.com> Co-authored-by: Kyle Spearrin <kyle.spearrin@gmail.com>
Usage
The SqlServerEFScaffold project is intended to be used as a tool for developers to validate their Microsoft SQL Server database changes and Infrastructure.EntityFramework.Models stay in sync for entity framework MS SQL Server repositories.
Check Infrastructure.EntityFramework.Models (Database First)
Run the following:
dotnet ef dbcontext scaffold "<local db connection string>" Microsoft.EntityFrameworkCore.SqlServer -o Model
The dotnet entity framework command will generate models from the local database provided.
Engineers can reference these models and validate they match with Infrastructure.EntityFramework.Models.
Check Microsoft SQL Server Database changes (Code/Model First)
Run the following:
dotnet ef migrations add Init
dotnet ef migrations script
This will generate a SQL script to initialize a database based on the models in Infrastructure.EntityFramework.Models.
This is helpful to check against the proposed database changes provided in /src/SQL