The detailed explanation of what Dapper is is omitted here; this article only provides a brief explanation of using Dapper in .NET Core. The code presented is mainly for examples, serving as an introduction. Developers can extend and adjust according to their own needs.
This is a very concise short article.
The Blazor series reprint has ended. In fact, the site owner finished reprinting on the 25th, synchronized it on the Dotnet9 website (https://dotnet9.com), and created an album "Learning Blazor Together Series", which everyone can browse at any time on the website.
TypeScript is excellent. It perfectly combines strong typing and rapid development, making it very useful. In many cases, I default to this library. However, no language is perfect; in some situations, TypeScript is not the most suitable tool:
I developed a tool to slim down .NET programs, which can delete referenced but unused assemblies. I used it to slim down a .NET Core program from `147 MB` to `59.5 MB`.
Yesterday we talked about unit testing, but sometimes due to time constraints, comprehensive testing is not possible.
The most boring part of developing a system is probably fixing bugs, especially errors like trying to access a null object (`Object reference not set to an instance of an object.`), which is the most common problem most people encounter when they first step into programming. To break free from the tedious bug-fixing process, this article introduces `unit testing`.
The framework `Zack.EFCore.Batch` for `batch` performing `update`, `delete`, and `insert` operations in `EF Core` has released a new version. The new version adds support for `.NET 6`, supports `ValueConverter` during batch data insertion, and completely solves the `"The count of columns should be even" exception that occurs when two column expressions are equivalent during data update`.
It was mentioned earlier that `ASP.NET Core Identity` uses `Claim`-based authentication. In fact, `ASP.NET Core Identity` has different types of authorization methods, the simplest being `Login Authorization`, `Role Authorization`, and `Claim Authorization`. However, all of the above are implemented in one way: Policy-based Authorization.
As mentioned earlier, `ASP.NET Core Identity` is based on `Claim` authentication, and `Role` is a `Claim` with type `Role`