why you don't need to abstract away ef core with clean architecture
Published 1 year ago • 45K plays • Length 10:55Download video MP4
Download video MP3
Similar videos
-
12:06
don't break the clean architecture rules with ef core
-
12:39
the best way to implement soft deletes with ef core (and why you shouldn't)
-
11:25
ef core 8 finally fixes value objects
-
8:01
clean up your ef core exceptions with this library
-
0:27
you need to master the ef core fluent api
-
0:32
the cleanest way to configure ef core
-
0:21
auto include ef navigation properties with this trick #shorts
-
15:15
what is a message queue rabbitmq and masstransit integration
-
13:54
how to use value objects to solve primitive obsession
-
18:06
mapping domain-driven design concepts to the database with ef core
-
0:31
don't use this ef core performance trick #shorts
-
0:33
this is how to implement ef core soft deletes
-
14:56
fix your controllers by refactoring to minimal apis
-
0:37
querying columns not in the ef model? here's how with shadow properties #shorts
-
0:29
this is how you can enforce your modular architecture
-
0:49
ef core - lazy loading, eager loading, and explicit loading
-
0:41
this is why you need distributed tracing
-
0:37
this is how ef keeps you safe from sql injection
-
0:26
don't hard code numbers - do this instead
-
0:42
c# records are immutable - but not if you do this
-
0:41
don't use the iserviceprovider for this? it depends...
-
0:18
it's not really "asynchronous"