EfCore.TestSupport
roundhouse
Our great sponsors
| EfCore.TestSupport | roundhouse | |
|---|---|---|
| 2 | 5 | |
| 347 | 916 | |
| - | 0.0% | |
| 0.0 | 2.8 | |
| 19 days ago | about 2 months ago | |
| C# | C# | |
| GNU General Public License v3.0 or later | - |
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.
roundhouse
-
REST API using C# .NET 7 with MySql
Before we can start using Postgres we need to create a table to store our data. I will be using excellent roundhouse database deployment system to execute database migrations.
-
Best db migration tool options to use along with Entity Framework
https://github.com/chucknorris/roundhouse is interesting, but rougher around the edges.
-
Is it sensible to run EF migrations at startup?
At my work we use https://github.com/chucknorris/roundhouse
-
Relational databases aren’t dinosaurs, they’re sharks
For our projects at work we use sqlserver and use a tool called roundhouse for migrations. https://github.com/chucknorris/roundhouse
-
Source control/release management for databases
Have a look at roundhouse too, if you have SQL experienced people this should be easy to use. All the migrations are basically sql scripts that you can version control. https://github.com/chucknorris/roundhouse
What are some alternatives?
DbUp - DbUp is a .NET library that helps you to deploy changes to SQL Server databases. It tracks which SQL scripts have been run already, and runs the change scripts that are needed to get your database up to date.
FluentMigrator - Fluent migrations framework for .NET
Flyway - Flyway by Redgate • Database Migrations Made Easy.
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.
Horton - Horton is the simple database migration utility.
dotnet-script - Run C# scripts from the .NET CLI.
PurefunctionPipelineDataflow - My Blog: The Math-based Grand Unified Programming Theory: The Pure Function Pipeline Data Flow with principle-based Warehouse/Workshop Model