When using an ASP.NET Core hosted project, the host project is capable of performing content negotiation and serving the statically-compressed files. The following compression algorithms are used:īlazor relies on the host to the serve the appropriate compressed files. When a Blazor WebAssembly app is published, the output is statically compressed during publish to reduce the app's size and remove the overhead for runtime compression. For more information, see ASP.NET Core Blazor Startup. Customize how boot resources are loadedĬustomize how boot resources are loaded using the loadBootResource API.
For more information, see ASP.NET Core Blazor globalization and localization.
The size reduction is particularly dramatic when disabling globalization. NET WebAssembly build tools installed, runtime relinking is performed automatically when an app is published. For more information, see Tooling for ASP.NET Core Blazor. Runtime relinking requires installation of the.
Run google deployed api vba code#
NET WebAssembly runtime trims unused runtime code and thus improves download speed. NET runtime ( dotnet.wasm) that the browser must download when the app is first accessed by a user's browser. One of the largest parts of a Blazor WebAssembly app is the WebAssembly-based. Blazor WebAssembly apps that are CPU intensive generally benefit the most from AOT compilation. Whether this tradeoff is worth using AOT compilation depends on your app. This means that using AOT compilation trades off load time performance for runtime performance. Although the size difference depends on the app, most AOT-compiled apps are about twice the size of their IL-compiled versions. The size of an AOT-compiled Blazor WebAssembly app is generally larger than the size of the app if compiled into. Reducing the build time for AOT compilation is under development for future releases of ASP.NET Core. AOT compilation isn't used when the project is run during development ( Development environment) because AOT compilation usually takes several minutes on small projects and potentially much longer for larger projects. WebAssembly AOT compilation is only performed when the project is published. NET Intermediate Language (IL) linking is also run to reduce the size of the published app: dotnet publish -c Release Publishing the Release configuration ensures the. To compile the app to WebAssembly, publish the app. To enable WebAssembly AOT compilation, add the property set to true to the Blazor WebAssembly app's project file: NET WebAssembly build tools, see Tooling for ASP.NET Core Blazor. The drawback to using AOT compilation is that AOT-compiled apps are generally larger than their IL-interpreted counterparts, so they usually take longer to download to the client when first requested.įor guidance on installing the. The AOT performance improvement can yield dramatic improvements for apps that execute CPU-intensive tasks. NET code directly into WebAssembly for native WebAssembly execution by the browser. AOT compilation addresses this performance issue by compiling an app's. NET code is interpreted, apps typically run slower than they would on a server-side. NET Intermediate Language (IL) interpreter implemented in WebAssembly. Without enabling AOT compilation, Blazor WebAssembly apps run on the browser using a. AOT compilation results in runtime performance improvements at the expense of a larger app size. This strategy is covered in the Standalone deployment section, which includes information on hosting a Blazor WebAssembly app as an IIS sub-app.īlazor WebAssembly supports ahead-of-time (AOT) compilation, where you can compile your.
This strategy is covered in the Hosted deployment with ASP.NET Core section.
0 kommentar(er)
