The day before yesterday, I added verified and failed display content to 'Blog.razor'. However, if the system wants to present the same content that failed to verify, it would be a waste of time to write it in every Component. You can use 'App.razor' to help us do unified presentation.
We mentioned earlier that `UserAuthentication()` and `UserAuthorization()`. The difference between the two is that the former is used to verify who the login person is, and the latter determines what the login person can do.
The verification done yesterday was only for the Identity system and was not included in our log
Today's part of implementing authentication
When developing a system, recording is a very important thing. It has not been mentioned before. I only thought of this recently, so let's implement it!
In most websites, uploading pictures is also a very important function. Today we will do it.
Suppose there is a situation like this today: there is a log entry, and a second entry is added but before submitting it, I want to delete the first entry. What will happen at this time?
The next step is to talk about the content associated with the database. We will focus on ASP.NET Core and EF Core. If there is a need to change the page, we will talk about Blazor. We will spend more space here.
We now have a basic log, but it will be reset every time we enter and reload the page data, because these data only exists in the browser and is not actually stored in the database. In order to save it, we need to connect to the database.
Sometimes I want to set individual styles for different Components, but if I write the classes in `wwwroot/css/site.css`, or change the style for a certain element, changing one may affect all Components. This global conflict must be avoided, but what should I do?