Back in ASP.NET 4, I really liked the way that it supported running migrations and seeding of the database for you. But in ASP.NET Core and EF Core, that hasn't come to the table yet.
I doubt it actually needs to happen because since ASP.NET Core gives you much more control over the life cycle of the web project. In Entity Framework Core, I've been using an approach to run migrations and seed the database that I kind of crufted together in the Betas. I don't think it's working.
Vue.js by Example (Now Available) |
Bootstrap 4 by Example |
Intro to Font Awesome 5 (Free Course) |
Application Name | WilderBlog | Environment Name | Production |
Application Ver | v4.0.30319 | Runtime Framework | x86 |
App Path | D:\home\site\wwwroot\ | Runtime Version | .NET Core 4.6.27129.04 |
Operating System | Microsoft Windows 10.0.14393 | Runtime Arch | X86 |