I'm experiencing the same issue as Blazor: Error on adding new scoped CSS since last update #55998

[Rod-at-DOH]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Hi @javiercn I am having the same issue that was reported last year. I'm using VS 2022 Enterprise Edition. I've added a CSS file, which I tried to associate with a .razor file. It looks fine, within VS 2022:

However, I get "The scoped css file (filename.razor.css) was defined but no associated razor component or view was found for it.."

I get that error when I build the solution within VS 2022. And I get the same error when I do a dotnet build in the command line.

I've edited the .csproj file but I don't see any Content ItemGroup, nor a <Content Remove... in the .csproj file.

What else should I try?

Expected Behavior

I expected the addition of the .CSS file to the .razor file to work without an problems.

Steps To Reproduce

I'm sorry, but this project is within our GitHub Enterprise organization, so I can't share it with you.

Exceptions (if any)

no exceptions

.NET Version

9.0.304

Anything else?

Here is what I got when I ran dotnet build:

FPTimetrackCore.Client failed with 1 error(s) (0.4s)
Pages\InputTimeForUser.razor.css : error BLAZOR102: The scoped css file 'Pages\InputTimeForUser.razor.css' was defined but no associated razor component or view was found for it.
FPTimetrackCore.Library succeeded (1.7s) → FPTimetrackCore.Library\bin\Debug\net9.0\FPTimetrackCore.Library.dll
FPTimetrackCore.API succeeded (1.8s) → FPTimetrackCore.API\bin\Debug\net9.0\FPTimetrackCore.API.dll
FPTimetrackCore.DataActionsAPI succeeded with 8 warning(s) (0.9s) → FPTimetrackCore.DataActionsAPI\bin\Debug\net9.0\FPTimetrackCore.DataActionsAPI.dll
C:\GitHub\PROD\FPTimetrackCore\FPTimetrackCore\FPTimetrackCore.DataActionsAPI\Program.cs(100,36): warning CS8600: Converting null literal or possible null value to non-nullable type.
C:\GitHub\PROD\FPTimetrackCore\FPTimetrackCore\FPTimetrackCore.DataActionsAPI\Program.cs(222,34): warning CS8600: Converting null literal or possible null value to non-nullable type.
C:\GitHub\PROD\FPTimetrackCore\FPTimetrackCore\FPTimetrackCore.DataActionsAPI\Program.cs(270,31): warning CS8600: Converting null literal or possible null value to non-nullable type.
C:\GitHub\PROD\FPTimetrackCore\FPTimetrackCore\FPTimetrackCore.DataActionsAPI\Program.cs(298,29): warning CS8600: Converting null literal or possible null value to non-nullable type.
C:\GitHub\PROD\FPTimetrackCore\FPTimetrackCore\FPTimetrackCore.DataActionsAPI\Program.cs(366,29): warning CS8600: Converting null literal or possible null value to non-nullable type.
C:\GitHub\PROD\FPTimetrackCore\FPTimetrackCore\FPTimetrackCore.DataActionsAPI\Program.cs(58,36): warning CS8600: Converting null literal or possible null value to non-nullable type.
C:\GitHub\PROD\FPTimetrackCore\FPTimetrackCore\FPTimetrackCore.DataActionsAPI\Program.cs(56,17): warning CS8321: The local function 'GetConnectionObject' is declared but never used
C:\GitHub\PROD\FPTimetrackCore\FPTimetrackCore\FPTimetrackCore.DataActionsAPI\SetConnectionString.cs(10,22): warning CS0169: The field 'SaveData.productionData' is never used

[javiercn]

@Rod-at-DOH thanks for contacting us.

Can you try with the latest 10.0.100 SDK build from the nightly build from dotnet/sdk?

Can you check if the following snippet unblocks you?

<ItemGroup>
  <!-- For component-scoped styles -->
  <Content Update="**\*.razor.css">
    <RazorComponent>%(RelativeDir)%(Filename)</RazorComponent>
  </Content>
  <None Update="**\*.razor.css">
    <RazorComponent>%(RelativeDir)%(Filename)</RazorComponent>
  </None>

  <!-- For view-scoped styles -->
  <Content Update="**\*.cshtml.css">
    <View>%(RelativeDir)%(Filename)</View>
  </Content>
  <None Update="**\*.cshtml.css">
    <View>%(RelativeDir)%(Filename)</View>
  </None>
</ItemGroup>

[Rod-at-DOH]

@javiercn that is an interesting question. To test using the latest build of 10.0.100 SDK would mean I'll have to install it. And that requires administrative privileges, which no developer where I work is allowed to have. Our CISO is very strict and non-communicative, so whenever I ask for something, I never hear back. However, I do have an arrangement so that once a month I can apply updates to my machine. I maintain a list of applications needing updates. Normally I try to get at least 3 things needing updates, before I ask for administrative privileges to apply the updates. Once that's done, they take the privileges away PDQ. I did that about 2 weeks ago. I hate to bring this up so soon after having done so recently, as that tends not to work well. That and the fact that VS 2026 and .NET 10 are currently in beta until November, may not sit well with my CISO. However, this is a project which has a deadline, so maybe I can successfully argue for it. Tomorrow is October 1st, so I'll try it then.

[javiercn]

@Rod-at-DOH If it's that much trouble don't worry about trying the nightly. I asked because I suspect it's an issue that's likely fixed in the 10.0 SDK.

I'd like to also mention that you don't need to install the nightly build on the machine.
You can download the dotnet nightly zip, extract it and configure a couple of environment variables $env:DOTNET_ROOT and $env:Path = "$($env:DOTNET_ROOT);$env:Path" on a terminal.

With this, you can do dotnet build against your solution and it should use the downloaded SDK. If you want to be sure you can run dotnet --info

Nothing gets installed nor persists beyond that terminal session.

As an alternative, it would help if you can instead create a minimal repro project as a public github repository, since we aren't able to reproduce this issue locally. And/Or capture an MSBuild binary log that we could inspect.

Finally, did the MSBuild snippet that I provided not help?

[Rod-at-DOH]

@javiercn I confess I read your recommendation wrong, so I didn't use it. I've now got the .csproj file open and see something odd there:

  <ItemGroup>
    <Content Remove="Pages\InputTimeForUser.razor" />
  </ItemGroup>

  <ItemGroup>
    <Compile Include="Pages\InputTimeForUser.razor" />
  </ItemGroup>

I'll remove those lines and put in the ones you suggested 4 hours ago. I'll let you know how it goes.

[Rod-at-DOH]

@javiercn I just added the lines of XML code to the .csproj file, and that appears to have resolved the issue. I can build it within VS 2022. And it builds fine at the command line using dotnet build. So, thank you! I never would have come up with that by myself. What do those lines of code do?