diff --git a/aspnetcore/blazor/webassembly-lazy-load-assemblies.md b/aspnetcore/blazor/webassembly-lazy-load-assemblies.md
index ee004151ff..a20b73efd0 100644
--- a/aspnetcore/blazor/webassembly-lazy-load-assemblies.md
+++ b/aspnetcore/blazor/webassembly-lazy-load-assemblies.md
@@ -12,6 +12,17 @@ uid: blazor/webassembly-lazy-load-assemblies
 
 [!INCLUDE[](~/includes/not-latest-version.md)]
 
+<!-- UPDATE 8.0 Remove NOTE when 
+                https://github.com/dotnet/AspNetCore.Docs/issues/31039
+                is worked. -->
+
+:::moniker range=">= aspnetcore-8.0"
+
+> [!IMPORTANT]
+> The examples in this article are based on Dynamic-Link Libraries (`.dll` file extension). This article hasn't been updated for Blazor in .NET 8, which uses the [Webcil packaging format for .NET assemblies](xref:blazor/host-and-deploy/webassembly#webcil-packaging-format-for-net-assemblies) (`.wasm` file extension). To use the guidance in its current form, substitute "`.wasm`" for "`.dll`" in the instructions. This article will be updated for Webcil packaging shortly, which is tracked by [Update from DLL to WASM files 8.0 (dotnet/AspNetCore.Docs #31039)](https://github.com/dotnet/AspNetCore.Docs/issues/31039).
+
+:::moniker-end
+
 Blazor WebAssembly app startup performance can be improved by waiting to load app assemblies until the assemblies are required, which is called *lazy loading*.
 
 This article's initial sections cover the app configuration. For a working demonstration, see the [Complete example](#complete-example) section at the end of this article.