Last night I was working on a project that had some many to many database relationships. On one side of the relationship, someone decided to use zero as the default “nothing selected” sort of key. This simply doesn’t work with Entity Framework, or probably most other .NET ORMs.
Entity Framework and the Magic of Nothing
posted on January 26, 2018 by long2know in Core, Entity Framework
Entity Framework Core “AsQueryable” Issue
posted on August 11, 2017 by long2know in Core, Entity Framework
Earlier, I was dinking around with some base code I wrote for EF 6.x and recently ported over to EF Core. It’s a nice bit of code that can build LINQ expressions for nearly any search/query scenario regardless of the domain models behind the scenes. It utilizes the LINQ Expression libraries and some reflection. The code works fine in EF 6.x, but I ran into a weird issue when building expressions for many-to-many relationships.
.NET Core Logging Levels and Categories
posted on July 20, 2017 by long2know in ASP.NET, Core, Entity Framework
Previously, I blogged about creating a Entity Framework based Logger in .NET Core. One thing that I never implemented was granular control of logging specific levels by category. It turns out that it’s pretty easy to do, though.
Entity Framework Multitenancy
posted on May 21, 2017 by long2know in Core, Entity Framework
At Build last week, the possibility to have global filters applied to a context opened the possibility to support multi-tenancy scenarios directly. Multi-tenancy is the concept of having specific users, or “tenants”, having access to, or ownership of, only their data. In the past, I have simply checked a user’s role and conditionally added filters. Pushing this into a global filter, though, seems a bit more practical.
Entity Framework Core 2.0 Trace Strings
posted on May 21, 2017 by long2know in Core, Entity Framework
In a previous post, I demonstrated a bit of code that uses Reflection to retrieve a proper materialized trace string from Entity Framework 1.1. The 2.0 preview release of EF broke that code, though.
Porting to .NET Core (Part 2)
posted on April 27, 2017 by long2know in Core, Entity Framework
A while back, I started looking at ways to port EF6 code, that uses a lot of the API hooks and such, to Entity Framework Core. Over the past week, I managed to port a large scale application that was using EF6 to utilize EF Core. Here are some observations/tips in continuing with my Dotnet Core porting.
Porting to .NET Core
posted on April 23, 2017 by long2know in Core, Entity Framework
I spent the better part of my development time this weekend porting various code from the .NET “full” framework to .NET Core. This included porting EntityFramework 6.1.3 code to EntityFramework Core 1.1.1. It was about as big of a pain as you would expect.
.NET and SQL Recursion
posted on February 23, 2017 by long2know in ASP.NET, Database, Entity Framework, LINQ
A while back, I wrote an application that processes sales information. These sales actually represent a hierarchy of data because there can be refunds, charge backs, charge backs of charge backs, refunds of refunds, adjustments, and so on and so forth. The way the data processing is handled, though, treating the entire hierarchy as a single transaction is important. This requires a bit of recursion.
Memory Leaks in .NET Tasks
posted on February 3, 2017 by long2know in ASP.NET, Entity Framework, Ninject
A while back, I blogged about a handy task scheduler and repeater. I use this code often and when I started using it with a heavy memory/data footprint, some serious memory leaks came to light.
SqlMetaData Gotcha
posted on January 18, 2017 by long2know in ASP.NET, Database
In one of my previous posts, I detailed using Table Value parameters. That method works great for my uses. However, I ran into one gotcha worth pointing out.