dotnet / aspnetcore

ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.

Home Page:https://asp.net

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Create 6.0 BlazorWebAssemblyApp project with the command and run the "dotnet publish" command, for the first time meet error:'MSB4018: The "GetFileHash" task failed unexpectedly'.

v-wenkecheng opened this issue · comments

Azure DevOps work item: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1484614?src=WorkItemMention&src-action=artifact_link

INSTALL STEPS
1.Clean M1 macOS machine
2. Install SDK 6.0.200 arm64 from:https://dotnet.microsoft.com/en-us/download/dotnet/6.0

Testcases Affected
[6.0]BlazorWebAssemblyWithPWANoAuth
[6.0]SignalRWithBlazorWebAssembly

Platform

  • Windows
  • macOS
  • Linux

Repro Steps

  1. Open terminal.
  2. Rundotnet new blazorwasm -o BlazorWasmApp_net60the command line.
  3. cd BlazorWasmApp_net60
  4. Run dotnet run
  5. Run dotnet publish

Actual Result

  1. Run the "dotnet publish" command, for the first time meet error:'MSB4018: The "GetFileHash" task failed unexpectedly'.
    MicrosoftTeams-image (8)
  2. Run the "dotnet publish" command again a second time, it will work fine, no error.

MicrosoftTeams-image (9)

The following publish error file is IDELog.
publish error.rtf.zip

EXPECTED
Running the "dotnet publish" command with the command works fine without errors.

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

commented

Closing as the issues was fixed internally.

Internal tracking issue was reactivated.

commented

Closing as the internal ticket has been resolved.