Static assets doesn't serve content files that are linked from a location outside of the project

[DamianEdwards]

When creating a Razor Class Library, files that are linked to wwwroot from a different physical location, e.g. a Shared directory one level up from the class library project, result in a 404 when requested via the usual _content/MyRazorClassLib/FileName path.

MyRazorClassLib.csproj

<Project Sdk="Microsoft.NET.Sdk.Razor">

  <PropertyGroup>
    <TargetFramework>net8.0</TargetFramework>
    <Nullable>enable</Nullable>
    <ImplicitUsings>enable</ImplicitUsings>
  </PropertyGroup>

  <ItemGroup>
    <Content Include="..\Shared\MyIcon.ico" Link="wwwroot\MyIcon.ico" />
  </ItemGroup>

  <ItemGroup>
    <SupportedPlatform Include="browser" />
  </ItemGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.Components.Web" Version="8.0.0-rtm.23512.10" />
  </ItemGroup>

</Project>

Component1.razor

<div class="my-component">
    This component is defined in the <strong>MyRazorClassLib</strong> library.<br />

    <h4>Linked file</h4>
    <img src="_content/MyRazorClassLib/MyIcon.ico" />

    <h4>Physical file</h4>
    <img src="_content/MyRazorClassLib/MyIconPhysical.ico" />
</div>

[mkArtakMSFT]

@DamianEdwards how did the second icon got loaded (in the network tab) ?

[DamianEdwards]

Repros on .NET 7 too AFAICT.

To learn more about what this message means, what to expect next, and how this issue will be handled you can read our Triage Process document.
We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. Because it's not immediately obvious what is causing this behavior, we would like to keep this around to collect more feedback, which can later help us determine how to handle this. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact work.