Solutions Architect | Developer | Blogger
Solutions Architect | Developer | Blogger
When I first started working seriously with Entity Framework Core, I treated it very simply. A string is a string, an int is an int, a DateTime is a DateTime. Life was easy. Then real business requirements arrived. Not tutorial…
When I first started using EF Core in real projects, performance was not something I worried about too much. Most examples online worked fine, the database was small, and the business requirements were still simple. I honestly thought performance tuning…
When I first started using Entity Framework Core, I had this feeling that everything was almost magical. I write some LINQ, hit Run, and boom, data comes back. At the beginning, that felt amazing. But later, when projects became bigger…
When I first started using Entity Framework Core seriously, I thought transactions were something “already handled by the database”. I remember thinking, why should I worry about transactions when SQL Server already knows how to keep data safe? That mindset…
I always tell people that EF Core is one of those tools that looks very simple in the beginning. You do a few queries, call ToList, and everything feels fine. Then the business side comes in and suddenly you are…
If you have been working with EF Core for a while, you probably stumbled on something called tracking and no tracking queries. When I first encountered these, I honestly did not pay much attention. I thought EF Core was smart…
When I started working with Entity Framework Core (EF Core), unit testing wasn’t something I gave much attention to. I was more focused on building features that worked. But as my projects grew bigger, especially in systems where business rules…
When I first tried using EF Core with Minimal APIs, I honestly thought it would be just a smaller version of a regular Web API controller setup. I was wrong. It’s simple, yes, but it forces you to think differently…
When I first started mixing EF Core with Blazor WebAssembly, I honestly thought it would be as simple as plugging in my DbContext on the client side and running some queries. I mean, why not, right? Just pull the data…
When I first started using EF Core inside an ASP.NET Core project, I honestly didn’t think too much about dependency injection. I just wanted to run queries, get data, and move on. But after a few projects and some mistakes…
