Keswiik Comments - Answer Overflow

my guess is business layer -> repo with tracking, maybe dbcontext isn't disposed of so it doesn't get GC'd business layer does shit with models business layer -> repo to save, attempt to track them with a new dbcontext blow up because first context is still floating around and tracking them

14 replies

CC#

•Created by Harry on 1/24/2025 in #help

Entity Framework Tracking not making changes to db

my best guess is that your repo is creating a new dbcontext for each call or something

14 replies

CC#

•Created by Harry on 1/24/2025 in #help

Entity Framework Tracking not making changes to db

$code

14 replies

CC#

•Created by Harry on 1/24/2025 in #help

Entity Framework Tracking not making changes to db

show code

14 replies

CC#

•Created by Core on 1/23/2025 in #help

✅ Proper way of using EF DbContext in a BackgroundService

All that means is "Use DBContextFactory if what you're injecting it into doesn't match the expected lifetime of a DBContext, but you have to dispose of it yourself"

10 replies

CC#

•Created by Core on 1/23/2025 in #help

✅ Proper way of using EF DbContext in a BackgroundService

Then you're misunderstanding what it's saying

10 replies

CC#

•Created by Core on 1/23/2025 in #help

✅ Proper way of using EF DbContext in a BackgroundService

Where? Because all I see is

Some application types (e.g. ASP.NET Core Blazor) use dependency injection but do not create a service scope that aligns with the desired DbContext lifetime.

10 replies

CC#

•Created by Core on 1/23/2025 in #help

✅ Proper way of using EF DbContext in a BackgroundService

https://learn.microsoft.com/en-us/ef/core/dbcontext-configuration/#use-a-dbcontext-factory any reason you can't use a dbcontextfactory?

10 replies

CC#

•Created by 77_105_114_111 on 1/16/2025 in #help

✅ Ignore case sensitive string in array.

show code with what you're trying to do

14 replies

CC#