Packaging of static assets of razor libraries is different in Githhub Actions from Local Computer

[rbuergi]

I had already asked the following issue: #60680. You have kindly explained to me how to configure the razor libs to create proper nuget packages. This setup works perfectly when I build the packages locally. I can also use them in a Blazor project, and all the js files get added to the staticwebassets folder.

However, when I try to build the razor library with the exact same commands on github actions under linux, I get warnings for the javascript files that

Warning: /usr/share/dotnet/sdk/9.0.202/Sdks/NuGet.Build.Tasks.Pack/build/NuGet.Build.Tasks.Pack.targets(221,5): warning NU5118: File '/home/runner/work/MeshWeaver/MeshWeaver/src/MeshWeaver.Blazor/wwwroot/arc--U5YtJTU.js' is not added because the package already contains file 'contentFiles/any/net9.0/wwwroot/arc--U5YtJTU.js' [/home/runner/work/MeshWeaver/MeshWeaver/src/MeshWeaver.Blazor/MeshWeaver.Blazor.csproj]

this pattern repeats for all javascript files.

In the published package, the js files get correctly added under contentFiles/any/net9.0/wwwroot, but they are missing from staticwebassets.

I have executed the exact same commands from the github action on my local machine, and the packages build fine. What's the difference between running the command on my local machine versus github actions? I really don't know how to advance on this; I wouldn't like to publish packages from my local PC....

[javiercn]

@rbuergi thanks for contacting us.

Capture an msbuild binlog and check the casing on the paths in the binlog.

[rbuergi]

Hi @javiercn. Thanks for resonding so quickly. This is the entire log from github actions. At least judging on my windows setup, the casings seem to be correct... However, I wonder why I get all the duplicate messages which I don't get on Windows.

job-logs.txt

[javiercn]

@rbuergi thanks for the additional details.

Unfortunately, the logs we need are the MSBuild binlogs generated with dotnet build /bl.

Alternatively, we would suggest you either create a new class library and start adding files until you are able to trigger the issue and provide a minimal repro.

[rbuergi]

@javiercn I am sorry I didn't understand. I have now produced the binlog for the pack process. It took me a while, I didn't even know this exists.

I guess this is what I need to do? If not, I am sorry. I know now how to produce this on github, so can also add the one for build.

Thanks a lot for taking care.

msbuild-binlog.zip