IDesignTimeDbContextFactory not always needed?

ASP.NET and EF Core - ModelState.IsValid always returns true for models generated by Scaffold-DbContext

As mentioned in @Smit's comment, you can use the ...-DataAnnotations... switch in the ...Scaffold-DbContext... command to generate the models with the correct validation annotations....See the documentation for ...Scaffold-DbContext... here: ...https://docs.microsoft.com/en-us/ef/core/miscellaneous/cli/powershell

Constructor injection into IDesignTimeDbContextFactory

By design..., the ...IDesignTimeDbContextFactory... isn't support to work with DI. One way to achieve this ...would be...:...public class AppDbContextFactory : IDesignTimeDbContextFactory<AppDbContext> { public AppDbContext CreateDbContext(params string[] args) { var options = new DbContextOptionsBuilder<AppDbContext>(); var config = Ge...

IDesignTimeDbContextFactory[TContext] violates the

The most common fix is to delete any migrations with the same name in your migrations folder, however if that doesn't work I'd suggest deleting all your migrations and dropping your database if it's been created....You should then be able to run ...Add-Migration CustomerDbContext -Context CustomerDbContext... and ...dotnet ef database update... wit...

Add an implementation of 'IDesignTimeDbContextFactory<ApplicationDbContext>' to the project

This can happen when EF don't know where the entry point to your application is. You ...do not... need to implement ...IDesignTimeDbContextFactory... if you're using ...BuildWebHost.... First of all, make sure that you are running your migration from the project containing the migrations....Eg... if you're using ...Package Manager Console...:...cd ...

Pass arguments to IDesignTimeDbContextFactory of EF Core

I had a similar issue recently trying to get an Asp.Net Core app to read the connection string. It turns out that you don't need the ...IDesignTimeDbContextFactory.... Instead, just make sure that your context has a paramerless constructor, and use something like this in the startup:...services.AddDbContext<ApplicationDbContext>(options => op...

DateTime.Now default value in entity configuration always sets the same DateTime in the database

Ok I figured out the issue....Because of the configuration:...builder.Property(x => x.EntityCreated).HasDefaultValue(DateTime.Now); ...When I created a migration, it was using the DateTime that was generated at the time of creating said migration. As a result, it made the default value for this field a static DateTime....To overcome this, I reverte...

Entity Framework Core, one-to-many relationship, collection always empty

You need to tell ...EF Core to load related entities.... One way is through ...eager loading...:...// notice the Include statement _Context.RootDataLists.Include(x => x.InsideDatas).First().InsideDatas

NuGet do I need to install Microsoft.EntityFrameworkCore if all I need is its provider?

If you are referencing a package via ...PackageReference..., you automatically get all of it's dependencies as well....Microsoft.EntityFrameworkCore.Sqlite 3.0.0... (targeting ....NETStandard 2.1...) depends on ...Microsoft.EntityFrameworkCore.Sqlite.Core 3.0.0..., which depends on ...Microsoft.EntityFrameworkCore.Relational 3.0.0..., which eventua...

EF Core always create .Annotation("SqlServer:Identity", "1, 1") on add-migration

Assuming you are using Core 3.0 or Core 3.1!...Add package Microsoft.EntityFrameworkCore.Relational...Also, you might need to explicitly specify the identity column in the mapping....builder.Property(o => o.Id).ValueGeneratedOnAdd().UseIdentityColumn();

Are auto-generated SQL database integer indices always greater than zero?

"If no negative ROWID values are inserted explicitly, then automatically generated ROWID values will always be greater than zero."...https://www.sqlite.org/autoinc.html