(21/30) Everyone learns Blazor together: ASP.NET Core Identity(1)
Today's part of implementing authentication
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?
Although Blazor does not require JavaScript, some existing js libraries are still very convenient and cannot be abandoned just because you don't want to use JavaScript. Blazor provides a method to call JavaScript. This situation is called JavaScript interoperability(abbreviated as JavaScript interop). This article will implement the reminder window of the Delete button, because deletion is a very important function and cannot be easily deleted by users with a single press.
The current four blogs come from fake data we have written, but normally we won't do this. Instead, there is a button for users to click to increase or decrease the number of blogs.
Yesterday I accidentally changed the type of Reset button to button, and changed it back to reset today.