EfCore.TestSupport
DbUp
EfCore.TestSupport | DbUp | |
---|---|---|
2 | 10 | |
348 | 2,089 | |
- | 0.7% | |
6.1 | 8.5 | |
24 days ago | about 2 months ago | |
C# | C# | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
EfCore.TestSupport
-
Repository pattern is a pain. Are there better ways?
If you have complex ef queries / functions mocking repository doesn't really make Sense. Your core application live in entity framework, you must test it. Author of best book about entity framework wrote lot blog posts about it (https://www.thereformedprogrammer.net/new-features-for-unit-testing-your-entity-framework-core-5-code/) maybe you can write extension methods on queryable and test it?
-
Is it sensible to run EF migrations at startup?
I think it would be fine for a small app. For larger apps: we currently use DbUp to run SQL scripts on deploy (in a seperate job, before the web app deploys) + https://github.com/JonPSmith/EfCore.TestSupport to run a unit test to ensure the EF Core schema matches the database to prevent errors at runtime.
DbUp
- How to Handle MSSQL Database in CI/CD?
-
create table in SqlDataProvider
I am not super familiar with SqlDataProvider, but its generally purpose is to interact with the DB at runtime, and not to migrate sql databases. I would probably use some ddl migration tool like DbUp, https://github.com/DbUp/DbUp, to handle table creation.
- Dev ,production best way to migrate migrations
- How do you do CI/CD with ef core
-
Best db migration tool options to use along with Entity Framework
I've used a simple migration tool called DbUp https://github.com/DbUp/DbUp
- Is it sensible to run EF migrations at startup?
-
Have to use SQL Server 2005 to pull data into a web application
Yea - it usually takes some diligence to maintain sprocs in a nice way. When my teams have used dapper in a production environment/application we usually combine it with something like dbup which lets us source control all of the objects/up/down scripts. It's like EF migrations but works with simple scripts.
-
Automate Manual SQL runs
Check out DbUp This is what we use and created a custom app that gets invoked within our pipeline
What are some alternatives?
roundhouse - RoundhousE is a Database Migration Utility for .NET using sql files and versioning based on source control
FluentMigrator - Fluent migrations framework for .NET
yuniql - Free and open source schema versioning and database migration made natively with .NET/6. NEW THIS MAY 2022! v1.3.15 released!
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
Entity Framework - EF Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, updates, and schema migrations.
Evolve - Database migration tool for .NET and .NET Core projects. Inspired by Flyway.
Unfold - Powershell-based deployment solution for .net web applications
Octo Pack - Creates Octopus-compatible NuGet packages
Flyway - Flyway by Redgate • Database Migrations Made Easy.