(7/30) Everyone learns Blazor together: Lifetime
All services you create must be registered with Startup.cs (Blazor Server) or Program.cs (Blazor WebAssemlby), but you don't have to do some basic services yourself.
All services you create must be registered with Startup.cs (Blazor Server) or Program.cs (Blazor WebAssemlby), but you don't have to do some basic services yourself.
Yesterday, I saw that the code of `FetchData.razor` was too long. For convenience, we extracted the part of `@code` and made it into another file.
C#'s GitHub page has a long list of tantalizing ideas, some of which are still being discussed.
The question arises, why does Blazor know that WeatherForecastService can be called here?
Most of the Windows Forms applications I encounter do not exist or have extremely low unit test coverage. And they are often difficult to maintain, with hundreds or even thousands of lines of code behind the various Form classes in the project, but it doesn't have to be.
Since I originally used ASP.NET Core API + Blazor Server, I will use Blazor Server to demonstrate it. I will make up for my experience after studying Blazor WebAssembly in the future.
After downloading Visual Studio, first create a Blazor solution, in which you can create a Blazor Server project. You can choose the location of the solution (Note: The new version of Visual Studio separates the Blazor Server and the new project template of Blazor WebAssembly, which is more intuitive)
The author's understanding of the website is the front-end, back-end and database. Users press a button or form request on the browser page to trigger front-end events and package the collected conditions and send them to the back-end
The author has not been in contact with the software industry for a long time and has been exposed to three architectures
If you've been following the latest trends in the. NET world, you've heard of Blazor by now.