net7: Razor class library - Missing CSS bundle in published package when built using msbuild /maxCpuCount

[hakenr]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Razor class library (Blazor) with CSS isolation.
Published as NuGet package using <GeneratePackageOnBuild>true</GeneratePackageOnBuild>.
Built using "C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\amd64\msbuild.exe" /m.
After upgrade to net7 and VS 17.4.0. the generated .nupkg does not include /staticwebassets/Name.bundle.scp.css. (all other static assets are present).

When the /m switch is removed from the msbuild call, the CSS file is present in the resulting .nupkg.
When the project is multi-targeted to net6+net7, the CSS file is present in the resulting .nupkg.
(Weird behavior observed with /m:1 switch. On our build server, the CSS file is there. On my dev-box, it is not.)

Expected Behavior

The generated .nupkg should contain the CSS bundle no matter which TargetFramework/maxCpuCount is used.

Steps To Reproduce

Unfortunately, I was not successful in reproducing the issue with a minimal project setup.

I prepared a setup (branch) in our repo which reproduces the issue:
https://github.com/havit/Havit.Blazor/tree/net7-msbuild-repro

Call msbuild with /m from project root directory to reproduce the issue:

"C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\amd64\msbuild.exe" /m

Output files (without CSS bundle):
.\Havit.Blazor.Components.Web\bin\Debug\Havit.Blazor.Components.Web.3.2.0.nupkg
.\Havit.Blazor.Components.Web.Bootstrap\bin\Debug\Havit.Blazor.Components.Web.Bootstrap.3.2.0.nupkg

Call msbuild without any switches and the CSS file will be in the output:

"C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\amd64\msbuild.exe"

Exceptions (if any)

No response

.NET Version

7.0.100

Anything else?

I was not sure in which repository should I file the issue. In the end I decided for aspnetcore as there is a good probability the issue is located in the .target files and/or build-tasks owned by the team?

[javiercn]

@hakenr thanks for contacting us.

Does it happen with MSBuild only or does it also happen with dotnet build?

File an issue through the Report a problem with Visual Studio - Visual Studio (Windows) | Microsoft Docs dialog and attach the binlog where the problem happens to it.

You can capture the binlog by adding /bl to the command-line. It will generate an msbuild.binlog file on the same folder from where msbuild is being invoked.

Hi @hakenr. 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.

[javiercn]

Razor class library (Blazor) with CSS isolation.
Published as NuGet package using <GeneratePackageOnBuild>true</GeneratePackageOnBuild>.
Built using "C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\amd64\msbuild.exe" /m.
After upgrade to net7 and VS 17.4.0. the generated .nupkg does not include /staticwebassets/Name.bundle.scp.css. (all other static assets are present).

Have you cleaned the bin and obj folders (to discard any intermediate state)

[hakenr]

Hi, I did some more experiments and tests and realized, that currently I'm not able to reproduce the issue as easily as I was this morning. Now, the /m parameter alone is not enough to make the CSS disappear. Now, it is the /m /p:DeployOnBuild=true combination which reproduces the issue (if I remove one or another, the issue disappears).

Smaller repo which currently reproduces the issue:
Havit.Bt.Blazor.zip

The binlogs
binlogs.zip

• msbuild-noCSS.binlog for "C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\amd64\msbuild.exe" /p:DeployOnBuild=true /m
• msbuild-plain.binlog for "C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\amd64\msbuild.exe"

Hope this helps diagnose this weird issue.

[javiercn]

@hakenr thanks for the additional details. Why are you passing DeployOnBuild=true for a razor class library?

[hakenr]

Why are you passing DeployOnBuild=true for a razor class library?

The RCL is just a part of a wider solution. The DeployOnBuild=true is included in our shared Azure Pipelines build definition (shared Task group) used by 100+ repos. The full msbuild.exe call usually looks like:

"C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\amd64\msbuild.exe" "W:\BuildAgents\BuildAgent5\515\s\Havit.Blazor.sln" /nologo /nr:false /fl /flp:"logfile=W:\BuildAgents\BuildAgent5\515\s\Havit.Blazor.sln.log;verbosity=normal" /dl:CentralLogger,"W:\BuildAgents\BuildAgent5\_tasks\VSBuild_71a9a2d3-a98a-4caa-96ab-affca411ecda\1.212.0\node_modules\azure-pipelines-tasks-msbuildhelpers-v3\tools\Microsoft.TeamFoundation.DistributedTask.MSBuild.Logger.dll";"RootDetailId=|SolutionDir=W:\BuildAgents\BuildAgent5\515\s|enableOrphanedProjectsLogs=true"*ForwardingLogger,"W:\BuildAgents\BuildAgent5\_tasks\VSBuild_71a9a2d3-a98a-4caa-96ab-affca411ecda\1.212.0\node_modules\azure-pipelines-tasks-msbuildhelpers-v3\tools\Microsoft.TeamFoundation.DistributedTask.MSBuild.Logger.dll" /p:IsDesktopBuild=True /p:SkipInvalidConfigurations=true /p:AutoParameterizationWebConfigConnectionStrings=False /p:PackageAsSingleFile=True /p:GenerateBuildInfoConfigFile=False /p:IncludeSetAclProviderOnDestination=False /p:DeployOnBuild=true /p:PublishDirectory="W:\BuildAgents\BuildAgent5\515\b" /p:SourceRevisionId=8c3d1c2c6d05649fd14068938a3f7e6fe0723b49 /p:TreatWarningsAsErrors=True /p:platform="Any CPU" /p:configuration="Release" /p:VisualStudioVersion="17.0" /m /p:_MSDeployUserAgent="VSTS_a77f2982-a11f-4768-b971-4d01fefae247_build_318_0"

(Above I tried to reduce the switches to the bare minimum where the issues reproduces)

[javiercn]

@hakenr I have moved this issue to the MSBuild repo. What I am observing is that in one case, the item "magically" disappears. So this might be related to a similar issue that we investigated recently.

From the binlog I can see that the item is correctly added as content:

When it gets here it is somehow ignored:

The relevant target is:

I might be missing something on my analysis, but if I am, I can't tell from the binlog where the item is being removed, and the definition is equivalent to the one for other files that are being included.

[hakenr]

@maridematte Hey, just a quick update. We ran into this issue again today - looks like it was either never fully fixed or got reintroduced in net9.0. It showed up after we dropped the net8.0 moniker and started targeting only net9.0:

-<TargetFrameworks>net8.0;net9.0</TargetFrameworks>
+<TargetFramework>net9.0</TargetFramework>

It seems to be related to the DeployOnBuild=true property, since the issue doesn't occur when publishing the NuGet package locally.

[maridematte]

Reopening so we can try to get a repro, and start tracking this once again.

[JaynieBai]

@maridematte It repros in net9.0 , net8.0 and 7.0.
I tried many times.
When using /m, the issue does not always reproduce. However, when using /m:3 and /p:DeployOnBuild=true together, the issue occurs more reliably and frequently.

Repro this issue with the following steps.
1. Download the project and change the TargetFramework to net9.0

Smaller repo which currently reproduces the issue:
Havit.Bt.Blazor.zip

2. msbuild /p:DeployOnBuild=true /m:3 /bl

Actual Results: In the package staticwebassets, some assets are missing.

From the binlog, the assets are lost in the _PackageFiles items

msbuild8175.binlog.txt