Migrating from EF 6.1.2 to EF Core (2.1). How to deal with the Migrations?

Trying to get ef core migrations to work on project migrated to .net core 2

<DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet" Version="1.0.0" /> ...You need to update to version 2.0.0.

Dealing with IReadOnlyCollection property in Entiry Framework Core 2.1

It's possible to configure a backing field usage for a navigation property, but not via ...Property... method which is for primitive property, and not via fluent API (doesn't exist at this time), but directly through mutable model metadata associated with the relationship:...modelBuilder.Entity<PurchaseOrder>() .HasMany(e => e.LineItems) .W...

Dealing with IReadOnlyCollection property in Entiry Framework Core 2.1

It's possible to configure a backing field usage for a navigation property, but not via ...Property... method which is for primitive property, and not via fluent API (doesn't exist at this time), but directly through mutable model metadata associated with the relationship:...modelBuilder.Entity<PurchaseOrder>() .HasMany(e => e.LineItems) .W...

EF Core 2.1 project Add-Migration NullReferenceException

Looks like this error was caused by some references to models in my ModelSnapshot class that did not exist anymore. Including some Identity models that were left behind after I removed ...AspNetCore.Identity... from the Context....Deleting the code below from my ...EscData01ContextModelSnapshot... fixed the issue....modelBuilder.Entity("Sms.Office....

.NET Core 2.1 and EF Framework 2.1

Despite the short-sited nature of .NET Core applications being hosted by IIS as a proxy front end, it appears that the AppPool running the IIS Proxy requires access to the same database server that the SQL Account used for the database requires... YUCK! ...Thanks to Edward (who posted a comment), it led me to this post:...https://weblog.west-wind.c...

.Net Core 2.1 EF Core Null Reference Exception when searching database with Where linq query

Turns out my Engine table had CompanyId instead of Company. All I had to do was change it to:...var context = _context.Engine .Include(e => e.EngineType) .Where(e => e.CompanyId == user.CompanyId);

EF Core 2.1 HasData() creating deletes and re-inserts for unchanged entities on subsequent migrations

This issue was an EF Core bug that ...was resolved... in EF Core 2.2.

Best way to coordinate atomic transactions between different business services in .NET Core / EF Core 2.1?

If your transaction extend across service boundaries that is so called ...Transactional integration antipattern.... ...One way to coupe with that issue is to use external orchestration service (for example ...Camunda...). It's responsibility would be to handle business flow and do some compensation actions on failure. It wouldn't be totally "transa...

How to Use EF Core 2.2.4 Data Library With Asp.Net Core 2.1 Project

The version of EF Core is tightly coupled with the version of ASP.NET Core you're using. Basically: EF Core 2.2.x only works on ASP.NET Core 2.2.x. You'll need to update the ...TargetFramework... to ...netcoreapp2.2... to make it work....Also, the recommended way to reference ASP.NET Core (in .NET Core 2.x projects) is to not include a specific ver...

Migrating from EF Core 2 to EF Core 3

use ...OrderByDesc()... for some property and then ...FirstAsync().... (...https://github.com/aspnet/EntityFrameworkCore/issues/18211...)...the invariant compare is not translated, was probably client evaluated previously. Depending on your database collation setting you could probably just do a normal equals here. ...Calling ...AsEnumerable()... o...

EF Core 2.1 Linq Query to EF Core 3.0

ok, i figured it out....here is my new code that works.... query = query.Where(x => x.Items.Where(o => o.BinItem != null && o.BinItem.Bin != null && o.BinItem.Bin.Zone != null ...