If they do, the file is only used to configure IIS-specific settings when hosted on IIS. Blazor apps don't typically have web.config files. ConfigurationĬonfiguration in ASP.NET Web Forms apps is typically handled using one or more web.config files.
This setup provides an additional level of security that prevents accidental exposing of project files over the web. Only the files in the Anything outside of the app's web root isn't web-addressable. Unlike ASP.NET Web Forms projects, not all files in a Blazor project can be requested as static files. We'll take a deeper look at the Startup class in the App startup section. In the Blazor WebAssembly app, the Startup class defines the root components for the app and where they should be rendered.
In the Blazor Server app, the Startup class is used to set up the endpoint for the real-time connection used by Blazor between the client browsers and the server. The Startup class is used to configure the app and any app-specific services. The WebAssembly app host doesn't, however, set up an HTTP server because it executes directly in the browser.īlazor apps have a Startup class instead of a Global.asax file to define the startup logic for the app.
File folder structure diagram code#
The code is similar in that it's setting up the app host to provide the same host-level services to the app. Public static IHostBuilder CreateHostBuilder(string args) =>īlazor WebAssembly apps also define an entry point in Program.cs. This code is mostly boilerplate and is often left unchanged. Examples of such services are configuration, logging, dependency injection, and the HTTP server. The web host manages the Blazor Server app's lifecycle and sets up host-level services. When the app executes, it creates and runs a web host instance using defaults specific to web apps. The Blazor Server app's entry point is defined in the Program.cs file, as you would see in a Console app. Instead of using the nfig file commonly found in ASP.NET Web Forms projects to reference packages, package references are added to the project file using the element. Transitive dependencies are included automatically. You only need to reference top-level package dependencies in. Most project dependencies are handled as NuGet package references. NET 5 both Blazor Server and Blazor WebAssembly app can easily share one unified runtime.Īlthough they're supported, individual assembly references are less common in. csproj file, most of which is explicitly listing the various code and content files in the project. Consequently, the project references the Blazor framework using individual package references.īy comparison, a default ASP.NET Web Forms project includes almost 300 lines of XML in its. NET into a web browser like you can on a server or developer machine.
The project file for a Blazor WebAssembly app looks slightly more involved (exact version numbers may vary): īlazor WebAssembly project targets instead of sdk because they run in the browser on a WebAssembly-based. The project file for the Blazor Server app is about as simple as it can get: Except for the hosting model-specific logic, most of the code in both projects is the same. You can follow the instructions to create either a Blazor Server app or a Blazor WebAssembly app hosted in ASP.NET Core. To create your first Blazor app, follow the instructions in the Blazor getting started steps. Here, we'll look at the structure of a Blazor project and compare it to an ASP.NET Web Forms project. Despite their significant project structure differences, ASP.NET Web Forms and Blazor share many similar concepts.
0 kommentar(er)
