To set the ASPNETCORE_ENVIRONMENT variable in Package Manager Console (PMC) , inside visual studio, to Production use this command first $env:ASPNETCORE_ENVIRONMENT=’Production’ Then you can use Update-Database normally.
If you’re using the DI container to manage the DbContext (i.e. you’re adding the DbContext to the service collection), the command timeout can be specified in the options. In Startup.ConfigureServices: services.AddDbContext<YourDbContext>(options => options.UseSqlServer( this.Configuration.GetConnectionString(“YourConnectionString”), sqlServerOptions => sqlServerOptions.CommandTimeout(60)) );
You can re-scaffold the model by running the command that you originally ran with the -Force option added. That will result in the contents of the specified folder being over-written. Using the Package Manager Console example from the EF Core docs, the revised command becomes: Scaffold-DbContext “Server=(localdb)\v11.0;Database=Blogging;Trusted_Connection=True;” Microsoft.EntityFrameworkCore.SqlServer -OutputDir Models -Force Alternatively, if you are … Read more
A note from documentation on the call to db.Database.EnsureCreated(): Note that this API does not use migrations to create the database. In addition, the database that is created cannot be later updated using migrations. If you are targeting a relational database and using migrations, you can use the DbContext.Database.Migrate() method to ensure the database is … Read more
Thanks to @Nkosi for pointing me to a link with an example of doing the same thing in EF 6: https://msdn.microsoft.com/en-us/library/dn314429.aspx. This didn’t work exactly as-is with EF Core, but I was able to start with it and make modifications to get it working. Below are the test classes that I created to “mock” IAsyncQueryProvider: … Read more
virtual was never required in EF. It was needed only if you want lazy loading support. Since Lazy loading is not yet supported by EF Core, currently virtual have no special meaning. It would when (and if) they add lazy loading support (there is a plan for doing so). Update: Starting with EF Core 2.1, … Read more
According to EF Core Docs, correct parameter name is -Target (for EF Core 1.1) or -Migration (for EF Core 2.0) so in your case: update-database -target test32 or update-database -migration test32 “Modern” way is to use “regular” command prompt and .NET Core CLI, and command like dotnet ef database update <target>
Support for stored procedures in EF Core 1.0 is resolved now, this also supports the mapping of multiple result-sets. Check here for the fix details And you can call it like this in c# var userType = dbContext.Set().FromSql(“dbo.SomeSproc @Id = {0}, @Name = {1}”, 45, “Ada”);
Like query supports wildcard characters and hence very useful compared to the string extension methods in some scenarios. For ex: If we were to search all the 4 lettered names with ‘ri’ as the middle characters we could do EF.Functions.Like(c.Name, “_ri_”); or to get all the customers from cities which start with vowels: var customers … Read more
This exception message doesn’t mean it requires a primary key to be defined in your database, it means it requires a primary key to be defined in your class. Although you’ve attempted to do so: private Guid _id; [Key] public Guid ID { get { return _id; } } This has no effect, as Entity … Read more