Arthur Vickers
Arthur Vickers
@luisf350 The code creates a single instance of your `DbContext` type in `MainWindowViewModel` and then uses this for evermore. Instead, create a new context instance for each unit-of-work.
@luisf350 The way you are using D.I. means that, as far as I can tell, you will never get more than one `DbContext` instance, because it is only (indirectly) requested...
@luisf350 It's hard to say because you know what your intention is. All I would say is that, if you are going to do a repository, with or without D.I.,...
Still repros on latest; regression from 7.
@dotnet/efteam Does anyone remember if there is a reason we are using all strings here?
@michaeltg17 This is by-design. EF Core cannot know whether or not the parameter or parameters that are passed to the constructor will resolve a `DbContextOptions` or not. Just because the...
Duplicate of #19756
Note for team: confirmed bug when iterating over tracked entities and detaching them. Note that this is typically anti-pattern. It is being done here because some other state is being...
Related to #27438
@RDoser Your projects are pulling .NET Framework assemblies into a .NET Core app. This is not supported.