-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Closed
Labels
✔️ Resolution: AnsweredResolved because the question asked by the original author has been answered.Resolved because the question asked by the original author has been answered.Status: Resolvedarea-blazorIncludes: Blazor, Razor ComponentsIncludes: Blazor, Razor Componentsfeature-blazor-aot-compilationThis issue is related to AoT compilation of Blazor WebAssembly appsThis issue is related to AoT compilation of Blazor WebAssembly appsfeature-blazor-wasmThis issue is related to and / or impacts Blazor WebAssemblyThis issue is related to and / or impacts Blazor WebAssemblyquestion
Description
This is a question not a bug report. I followed the steps here https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-6-preview-4/comment-page-2/#blazor-webassembly-ahead-of-time-aot-compilation to deploy a Blazor WASM app. I see effectively it reports in the output window of visual studio it is AOT'ing, but when I browse the app I see in Chrome developer tools it is downloading the dll's, so my question is whether I'm seeing the interpreted runtime application or AOT? How can I make sure?
IrinaPykhova and jacob-l
Metadata
Metadata
Assignees
Labels
✔️ Resolution: AnsweredResolved because the question asked by the original author has been answered.Resolved because the question asked by the original author has been answered.Status: Resolvedarea-blazorIncludes: Blazor, Razor ComponentsIncludes: Blazor, Razor Componentsfeature-blazor-aot-compilationThis issue is related to AoT compilation of Blazor WebAssembly appsThis issue is related to AoT compilation of Blazor WebAssembly appsfeature-blazor-wasmThis issue is related to and / or impacts Blazor WebAssemblyThis issue is related to and / or impacts Blazor WebAssemblyquestion