Developers choose Entity framework ORM (EF) for better productivity when accessing the database. But, when the product is built that went from bare bones to very complex and heavy data access then comes the performance.

Sometimes its the Entity framework that kills the performance so the choice when searching for a better ORM than Entity framework is Dapper.

In this post, I’ll walk you through how we can replace the existing entity framework code with dapper.

Annotating the controllers with ApiController attribute in ASP.NET Core 2.1 or higher will enable the behavioral options for the API’s. These behavioral options include automatic HTTP 400 responses as well.
In this post, we’ll see how we can customize the default error response from the ASP.NET Core Web API.

With the asp.net core modularity, the configuration and setup work for the asp.net core projects is more when compared to building apps with the .net framework.

In this post, we’ll explore how to build a web API and also look at the configuration options that we need to build a web API in asp.net core.

When I wanted to look at the IL of the C# code I wrote I used to create a new console application in visual studio and write the code and build it and view the DLL with ILSpy or dotPeek.

These days I’m using LINQPad to view the IL quickly.

Here is the alternative to that hectic setup, Sharplab.

SharpLab is developed by Andrey Shchekin. SharpLab is a similar tool you can use to Run, De-compile (C#, IL, JIT Asm) and visualizing syntax trees. You can also switch the C# language to whatever you want in SharpLab.

And the good thing about SharpLab is that you don’t need any tools except a web browser.

In the previous blog post, we looked at what event bubbling is and how we can implement it.

In this article we’ll see what is the difference between stopPropogation() and preventDefault() methods in an event handler.

Event bubbling concept is a way of propagating the events from the element clicked all the way to the ancestor. This is a beginner article so if you are already aware of this you can skip this article.

This post is a sequence for the previous article which shows why the Func delegate is not translated into the SQL statements.

This post as you read from the title is about unit testing for private methods. Do we really need to test the private methods in the unit tests?

In this post, I’ll show you what happens when you use a func delegate on the Entity Framework entities.

Filtering an item from a list of items is easy but if the item to filter is not known at compile time then filtering a list will be little complicated.