Simple setup. I have a Blazor WASM 9 client in Visual Studio 2022 that accesses the RCL which contains a wwwroot folder with js and css sub folders which contains some css and js files. If I add the RCL project as a project reference to the master project everything works as expected. You can see the mapping of _content in the browser sources tab in Chrome as well as all the reverent files. If you remove the RCL project, compile it to release and then add the dll to the project the resources are not mapping and the application reports 404 resources not found.
According to documentation the RCL css resource files should be mapping to:
<link href="_content/Common.Resources/css/site.min.css" rel="stylesheet" />
Note: Project name and Package name are the same "Common.Resources".
I can only assume that the project reference maps to the actual project but when I reference the dll the wwwroot is not embedded in the dll which documentation points out should be done automatically. I have checked the bin\net9.0 folder and did find Common.Resources.staticwebassets.endpoints.json manifest which contains the correct information to the resources but I'm not sure if this is proof that the resources were in fact embed in the dll or if this file is needed as a reference or if it should be embedded as well.
Just a note, the components in the RCL works as expected referenced as a project or as a dll minus the look and feel of course. There are also no conflicting resource files.
I have tried various different combinations and suggestions I found on the web.
Tried <link href="/css/site.min.css" rel="stylesheet" /> and a host of other variations.
Changed the css and js files from content to embedded resources.
I am using Grunt. I disabled processing and manually copied the files to verify it is not a question of the files not being there or still being generated when the assembly is build.
Repaired the Visual Studio installation. Yes I'm that desperate.
This should be simple! I'm at a loss here. What am I missing?