Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Building package.json with ClientAssets results in 404 Not Found #38898

Closed
AB017JH opened this issue Dec 8, 2021 · 2 comments
Closed

Building package.json with ClientAssets results in 404 Not Found #38898

AB017JH opened this issue Dec 8, 2021 · 2 comments
Labels
area-blazor Includes: Blazor, Razor Components feature-blazor-client-assets ✔️ Resolution: Duplicate Resolved as a duplicate of another issue investigate Status: Resolved

Comments

@AB017JH
Copy link

AB017JH commented Dec 8, 2021

Hello,

I have changed the semi-automatic build process to use the new alpha version ClientAssets NuGet following the blog and sample, unfortunately, it does not work for my case.
The npm install and build script ran fine. Outputting the correct .js files into the obj folder the set script in index file is in the current format

<script src="_content/ComponentsLibrary/749.js"></script>
<script src="_content/ComponentsLibrary/main.js"></script>

unfortunately getting the

749.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
main.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)

Using .net5.0, running Blazer hosted via http.sys
When using the semi-automatic build I was having the beforeBuild task in .csproj running the webpack and copying the file in the
ComponentsLibrary/wwwroot/dist that worked fine
webpack ./src/dockmanager.js -o ../wwwroot/dockManager.bundle"
now I have just
webpack ./src/dockmanager.js
which results in files being in the
"ComponentsLibrary\obj\Debug\clientassets\749.js"
"ComponentsLibrary\obj\Debug\clientassets\main.js"

Did I miss some configuration?

Thank you for your help,

Stanislav.

@TanayParikh TanayParikh added area-blazor Includes: Blazor, Razor Components feature-blazor-client-assets labels Dec 8, 2021
@mkArtakMSFT mkArtakMSFT added this to the .NET 7 Planning milestone Dec 8, 2021
@ghost
Copy link

ghost commented Dec 8, 2021

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. 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 issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@mkArtakMSFT
Copy link
Member

Thanks for contacting us.
Please note that .NET 5 is out of support already.
We're also going to address some of the remaining issues in this area as part of #38445

@mkArtakMSFT mkArtakMSFT closed this as not planned Won't fix, can't repro, duplicate, stale Aug 10, 2022
@mkArtakMSFT mkArtakMSFT added the ✔️ Resolution: Duplicate Resolved as a duplicate of another issue label Aug 10, 2022
@ghost ghost added the Status: Resolved label Aug 10, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Sep 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components feature-blazor-client-assets ✔️ Resolution: Duplicate Resolved as a duplicate of another issue investigate Status: Resolved
Projects
None yet
Development

No branches or pull requests

3 participants