Blazor and .NET6 creates an error: EntrypointInvoker in assembly Microsoft.AspNetCore.Components.WebAssembly

[erossini]

I have my simple project with Blazor. I updated the project from .NET5 to .NET6. I deploy to the production environment using Web Deploy. On the production server, I am getting this error

Error: Could not find class: Microsoft.AspNetCore.Components.WebAssembly.Hosting:EntrypointInvoker in assembly Microsoft.AspNetCore.Components.WebAssembly

The configuration of Web Deploy is

[TanayParikh]

Hello, thanks for contacting us. The EntrypointInvoker was removed in .NET 6 (via #31769). This seems to indicate the app is still TFM 5. Could you please show us what the .csproj looks like for this project?

Hi @erossini. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[erossini]

This is the csproj

<Project Sdk="Microsoft.NET.Sdk.BlazorWebAssembly">

  <PropertyGroup>
    <TargetFramework>net6.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly" Version="6.0.0" />
    <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly.DevServer" Version="6.0.0" PrivateAssets="all" />
    <PackageReference Include="System.Net.Http.Json" Version="6.0.0" />
  </ItemGroup>

  <ItemGroup>
    <ProjectReference Include="..\PSC.Blazor.Components.DataTable\PSC.Blazor.Components.DataTable.csproj" />
  </ItemGroup>

  <ItemGroup>
    <Content Update="wwwroot\img\psc_logo.png">
      <PackagePath>\</PackagePath>
      <Pack>True</Pack>
    </Content>
  </ItemGroup>

</Project>

[pranavkm]

@erossini do you also mind including the obj\project.assets.json for this file? It might be one of your references is causing an older version of blazor.webassembly.js to be used, instead of the 6.0.0 version, and the resolved package references might give us some hints. Alternatively, if there's a minimal app you could share with us that reproduces the problem, that would be great.

Hi @erossini. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[erossini]

This is the project.assets.json

project.assets.zip