From 7f0d20f696e187564161dae10ef59d1844a2b6b9 Mon Sep 17 00:00:00 2001 From: Luke Latham <1622880+guardrex@users.noreply.github.com> Date: Tue, 29 Mar 2022 06:43:14 -0500 Subject: [PATCH] Clarify build tool effect on size (#25456) --- aspnetcore/blazor/hosting-models.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/blazor/hosting-models.md b/aspnetcore/blazor/hosting-models.md index b20d729dbc..725c075a71 100644 --- a/aspnetcore/blazor/hosting-models.md +++ b/aspnetcore/blazor/hosting-models.md @@ -74,7 +74,7 @@ The Blazor WebAssembly hosting model has the following limitations: Blazor WebAssembly supports ahead-of-time (AOT) compilation, where you can compile your .NET code directly into WebAssembly. AOT compilation results in runtime performance improvements at the expense of a larger app size. For more information, see . -The same .NET WebAssembly build tools used for AOT compilation also [relink the .NET WebAssembly runtime](xref:blazor/host-and-deploy/webassembly#runtime-relinking) to trim unused runtime code resulting in a smaller app size and thus improved download speed. +The same .NET WebAssembly build tools used for AOT compilation also [relink the .NET WebAssembly runtime](xref:blazor/host-and-deploy/webassembly#runtime-relinking) to trim unused runtime code. Blazor WebAssembly includes support for trimming unused code from .NET Core framework libraries. For more information, see . The .NET compiler further precompresses a Blazor WebAssembly app for a smaller app payload.