roundhouse
Evolve
| roundhouse | Evolve | |
|---|---|---|
| 5 | 5 | |
| 915 | 825 | |
| -0.1% | - | |
| 2.8 | 2.8 | |
| about 2 months ago | 19 days ago | |
| C# | C# | |
| - | 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.
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
Evolve
-
How to Handle MSSQL Database in CI/CD?
If you want to stay in C# land, look at Evolve.
-
Can I export database from PostgreSQL and connect it to my C# app?
So, in general, one would use a versioned database schema that would connect to a database and execute a series of SQL files. For C# you have things like Evolve.
-
The correct way to source control data
So you don't really source control the data, but you do source control the database schema. A common way in the .net world to do this is to use something like evolve which basically allows you to version SQL scripts and have them executed on application launch.
-
Best db migration tool options to use along with Entity Framework
Been using https://github.com/lecaillon/Evolve for many years. Its a .Net Core equivalent to Flyway. You run plain old SQL scripts and just follow a file naming convention. It can run embedded inside a project, it has a .Net Tool and a standalone CLI. The SQL scripts can also be embedded in the executable or as external files.
-
Developing with SQL Server in .NET
I've been using Evolve in the past, very simple and effective.
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.
Entity Framework - EF Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, updates, and schema migrations.
Flyway - Flyway by Redgate • Database Migrations Made Easy.
FluentMigrator - Fluent migrations framework for .NET
Versioning.NET - A dotnet tool that automatically increments versions in csproj files based on git commit hints.
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
AutoTrimps - AutoTrimps - Zek
sqlancer - Automated testing to find logic and performance bugs in database systems
EfCore.TestSupport - Tools for helping in unit testing applications that use Entity Framework Core
key-value-store - Basic Key-Value Store built on top of YugabyteDB, .Net 7.0, and Entity Framework Core 7.0.