[StaticWebAssets] - 9.0.300 had caching issue about Razor compiling but 9.0.105 works.

[csarigul]

Describe the bug

Building a simple Razor project with .NET SDK 9.0.300 fails with a DefineStaticWebAssets error after first successful build. The same project builds fine with SDK versions 9.0.105 and 8.0.409.

To Reproduce

Use the following .csproj:

<Project Sdk="Microsoft.NET.Sdk.Razor">
  <PropertyGroup>
    <TargetFramework>net8.0</TargetFramework>
    <Nullable>enable</Nullable>
    <ImplicitUsings>enable</ImplicitUsings>
  </PropertyGroup>
  <ItemGroup>
    <FrameworkReference Include="Microsoft.AspNetCore.App" />
    <PackageReference Include="Microsoft.EntityFrameworkCore" Version="8.0.6" />
    <PackageReference Include="Microsoft.AspNetCore.Authentication.JwtBearer" Version="8.0.3" />
  </ItemGroup>
</Project>

Works with 9.0.105 and 8.0.409, but fails with 9.0.300 after first successful build.
Besides, If you check aspnetcore github repo (v9.0.5) you will see they're using 9.0.105 not 9.0.300.
https://github.com/dotnet/aspnetcore/blob/v9.0.5/global.json

Exceptions (if any)

C:\Program Files\dotnet\sdk\9.0.300\Sdks\Microsoft.NET.Sdk.Razor\targets\Sdk.Razor.CurrentVersion.targets(747,5): warning RAZORSDK1004: One or more Razor view or page files were found, but the project is not configured to add Razor support for MVC. The MSBuild property 'AddRazorSupportForMvc' must be set to correctly compile Razor files that target MVC. For more information, see https://go.microsoft.com/fwlink/?linkid=868374.
C:\Program Files\dotnet\sdk\9.0.300\Sdks\Microsoft.NET.Sdk.StaticWebAssets\targets\Microsoft.NET.Sdk.StaticWebAssets.JSModules.targets(106,5): error MSB4018:
The "DefineStaticWebAssets" task failed unexpectedly.
System.ArgumentException: An item with the same key has already been added. Key: F5aUHOC0pS/uDCGi8ST2NFxyR9EUB9ZoeAfi1rk9MBg=
at System.Collections.Generic.Dictionary2.TryInsert(TKey key, TValue value, InsertionBehavior behavior) at System.Collections.Generic.Dictionary2.Add(TKey key, TValue value)
at Microsoft.AspNetCore.StaticWebAssets.Tasks.Utils.HashingUtils.ComputeHashLookup(MemoryStream memoryStream, ITaskItem[] candidateAssets, Span`1 metadata)
at Microsoft.AspNetCore.StaticWebAssets.Tasks.DefineStaticWebAssets.GetOrCreateAssetsCache()
at Microsoft.AspNetCore.StaticWebAssets.Tasks.DefineStaticWebAssets.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(TaskExecutionHost taskExecutionHost, TaskLoggingContext taskLoggingContext, TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask)

Further technical details

.NET SDK:
Version: 9.0.300
Commit: 15606fe
Workload version: 9.0.300-manifests.af4147de
MSBuild version: 17.14.5+edd3bbf37

Runtime Environment:
OS Name: Windows
OS Version: 10.0.22631
OS Platform: Windows
RID: win-x64
Base Path: C:\Program Files\dotnet\sdk\9.0.300\

.NET workloads installed:
[wasm-tools-net8]
Installation Source: VS 17.14.36109.1
Manifest Version: 9.0.5/9.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\9.0.100\microsoft.net.workload.mono.toolchain.net8\9.0.5\WorkloadManifest.json
Install Type: Msi

[wasm-tools]
Installation Source: VS 17.14.36109.1
Manifest Version: 9.0.5/9.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\9.0.100\microsoft.net.workload.mono.toolchain.current\9.0.5\WorkloadManifest.json
Install Type: Msi

Configured to use loose manifests when installing new manifests.

Host:
Version: 9.0.5
Architecture: x64
Commit: e36e4d1a8f

.NET SDKs installed:
8.0.409 [C:\Program Files\dotnet\sdk]
9.0.105 [C:\Program Files\dotnet\sdk]
9.0.300 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
Microsoft.AspNetCore.App 8.0.16 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 9.0.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 9.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 8.0.16 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 9.0.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 9.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 8.0.16 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 9.0.4 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 9.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
x86 [C:\Program Files (x86)\dotnet]
registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

Environment variables:
Not set

global.json file:
Not found

Learn more:
https://aka.ms/dotnet/info

Download .NET:
https://aka.ms/dotnet/download

[csarigul]

@javiercn
For testing purposes, I patched dotnet CLI binaries with modified "Microsoft.NET.Sdk.StaticWebAssets.Tasks" project, it started working. I simply returned NoCache result.

If you like, I can debug that place and create PR with unit test.

[keba-lum]

I have the same problem

[lepned]

I have the same issue

[csarigul]

Running dotnet clean or using Visual Studio's Clean Solution does not remove the StaticAsset cache file (rpswa.dswa.cache.json) located in the obj directory.

Workaround:
Simply remove "obj" folder under project, than it should compile fine.

Also clear the "obj" folder each branch change. Otherwise you can face awkward problems like not finding not-existing web assets.

[sagharmax]

I also have this issue with my ASP.NET Core application after version 17.4. With two minor updates, I wonder why this issue has not been solved.

[LifeLongThinker]

Can confirm, I've come across this very issue multiple times (same specs as above).

As a temporary workaround, I am using version 9.0.204, as per my global.json:

{
  "sdk": {
    "version": "9.0.204",
    "rollForward": "disable"
  }
}

[sagharmax]

Thank you for confirming the issue and sharing the workaround. I’ll try locking the SDK version to 9.0.204 using global.json and see if it resolves the problem on my side. Hopefully, Microsoft will address this properly in an upcoming update.

[SMERKY]

Also worked for me after reverting to SDK version 9.0.204

[sedgey]

Can confirm the above temporary fix is working on a multi project solution with global.json in the root

[rburnham-def]

e

This worked for me, I installed .net framework 4.5.2 and all of a sudden a .Net core 8 project that was building started to fail. A clean / rebuild did not work but deleting the obj folder fixed it

[sagharmax]

After upgrading the .NET SDK to version 301, all problems were solved yesterday. Please upgrade and check it