EF Core, INotifyPropertyChanged

Eager Loading "No coercion operator is defined between types" after .NET Core/EF Core 2.0 Upgrade

Include... isn't useful in this situation as you are returning a projection and the ...Include...s are ignored (read about ignored includes ...here...)....If by "intended results" you mean you want ...record.PaperRecord.Paper... to have a value, simply include it in your projection; EF will wire up the relationship....new { PaperRecord = _.Pape...

Using automapper.collection in aspnet core & ef core doesn't updated edited records in a collection

Have you tried the Entity Framework Core repo? ...https://github.com/AutoMapper/AutoMapper.Collection.EFCore/tree/development

.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);

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...

What is the difference between EF Core Database-First and EF Core Code-First approaches?

Database-First...DB-First is that you reverse engineer an existing database to create an Entity Framework model.Instead of designing the EDMX manually and generating the SQL script to create the Database, we build the latter and then generate the former using the Entity Framework Designer tool....Code-First...Code-First uses migrations to create th...

INotifyPropertyChanged not called correctly with Entity Framework Core

For anyone else stumbling across issues with bindings using Entity Framework with observable objects, my underlying issue was that the ...SetProperty... method, which all properties call to update, was marked virtual in my base object. ...The effect was that the EF proxy was overriding this, which caused weird things to happen - the UI not updating...

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 ...

EF core 2.2 to EF core 3.1

Starting with 3.0, EF Core LINQ queries are no longer evaluated on the client. ...learn more: MSDN...Actually i think your problem may be in i.ForApplication Property if it makes some calculations.

Migrate .NET Core 2.2 to .NET Core 3.1 and keep referencing EF Core 2

It is possible to reference EF Core 2.0 from .NET Core 3.1 App?...Yes, totally. Doing the same - and then moving off to Ef 6.4 as it looks as the breaking changes are just not bearable. Spending days trying to get basics working....Isn't there some magic compatibility switch in .NET Core like Microsoft from time to time provides?...No. Breaking ...