Should Blazor AOT still be downloading dlls?

[srpeirce]

Describe the bug

When running AOT build I am seeing the blazor.wasm file increase size from 398KB to 3.6MB which matches my expectations.

However, I am also still seeing the dlls being downloaded, these look exactly the same files and sizes as per the non-AOT application. My assumption was that these would no longer be required, or would be .wasm instead?

To Reproduce

Load dev tools, clear application data. Navigate to AOT compiled site.

Dlls are still downloaded as well as wasm file.

Exceptions (if any)

Further technical details

Following notes from here: https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-6-preview-4/#blazor-webassembly-ahead-of-time-aot-compilation

Prerendering the wasm app in server project.

From the Client csproj:

<PropertyGroup>
    <TargetFramework>net6.0</TargetFramework>
    <ServiceWorkerAssetsManifest>service-worker-assets.js</ServiceWorkerAssetsManifest>
    <BlazorEnableTimeZoneSupport>false</BlazorEnableTimeZoneSupport>
    <BlazorWebAssemblyPreserveCollationData>false</BlazorWebAssemblyPreserveCollationData>
    <InvariantGlobalization>true</InvariantGlobalization>
    <RunAOTCompilation>true</RunAOTCompilation>
  </PropertyGroup>

I appreciate that I might not of fully understood how AOT is working, in which case I apologise for wasting time. I would appreciate a link to some more information as to how it all works :)

[javiercn]

@srpeirce thanks for contacting us.

I believe this is a known (temporary) behavior. @pranavkm can you confirm?

[ghost]

This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes.

See our Issue Management Policies for more information.