Build error throws when running dotnet pack with multiple target framework

[Karthigaiselvi-SF2856]

Bug Description:

After upgrading the .NET 6.0 preview 1 SDK, it throws build error when running dotnet pack command line. The problem is occur when the project file have multiple target frameworks <TargetFrameworks>netstandard2.0;net5.0</TargetFrameworks>. If I change it to single <TargetFramewok> then it works fine.

Exceptions (if any)

C:\Program Files\dotnet\sdk\6.0.100-preview.1.21103.13\Sdks\Microsoft.NET.Sdk.Razor\build\netstandard2.0\Microsoft.NET.Sdk.Razor.ScopedCss.targets(134,3): error MSB4044: The "ComputeCssScope" task was not given a value for the required parameter "TargetName". [D:\Feb\NET6\RazorClassLibrary2\RazorClassLibrary2.csproj]

To Reproduce

• Download the Razor sample.
• Goto command prompt and then run the command dotnet pack -c Release

Sample:

RazorClassLibrary3.zip

Further technical details

Blazor RazorClass Library 6.0 sample
Latest SDK .NET 6.0 Preview 1
VS 2019 preview

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[pranavkm]

Thanks for the issue report. @captainsafia this looks like a regression as part of our change to use a source generator. Static Web Assets appears to wire up to RazorComponentGenerate which is no longer invoked with source generators. I'm able to reproduce this with the latest SDK build.

[captainsafia]

I've been able to reproduce this on preview1 and preview2 so I don't think it's strictly related to source generators.

However, we'll likely have to make different modifications to the ordering for the source generator/non-source generator scenarios.

[silambarasan-ilango]

As per the above comment, this issue persists in v6.0.0-preview.2 released yesterday. @pranavkm / @captainsafia Can we have any tentative timeline to expect the fix or having any workaround in the meantime?

[skclusive]

any update on the issue?. still reproducible in v6.0.0-preview3. not able to multi target component libraries due to this issue. hope the issue will be fixed in next preview. thanks

[captainsafia]

@skclusive None yet. We're tracking it under next sprint planning. If you're affected by this, you can let us know by giving the issue a thumbs up.

[skclusive]

@captainsafia thanks. hope it will be considered for next sprint. would like to convey that this is more than a blazor bug. it is regression of basic expectation of dotnet cli. (dotnet pack to multi target C# library)

even tried the following from documentation with no luck. https://docs.microsoft.com/en-us/aspnet/core/blazor/components/css-isolation?view=aspnetcore-5.0

<DisableScopedCssBundling>true</DisableScopedCssBundling>

[kmuthukumar23]

@pranavkm / @captainsafia - Any updates for this? Can you please share any expected timeline for the fix?

[captainsafia]

@kmuthukumar23 We haven't had the chance to look at this yet. If this issue impacts you, the best thing to do is to give the original issue a thumbs up. This helps us out when we do triage to identify which issues need to be fixed.

I've gotten as far as reproducing this and starting to tinker with the binlog to see what's up but haven't landed on a fix.