Blazor has 3 different ways of binding data on the client-side.
Here are the different data binding mechanisms in the client-side blazor framework.
- One-way data binding
- Two-way data binding
- Component parameters
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.
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.
Update your browser to view this website correctly. Update my browser now