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

Problem with Blazored Modal #13

Closed
peerem opened this issue Mar 13, 2021 · 5 comments
Closed

Problem with Blazored Modal #13

peerem opened this issue Mar 13, 2021 · 5 comments
Labels
bug Something isn't working

Comments

@peerem
Copy link

peerem commented Mar 13, 2021

We get this error, if we open a "Blazored Modal" window. It runs fine in Blazor WebAssembly, Blazor Server full or running on Chromely.

https://github.com/Blazored/Modal

BlazoredModal

@peerem
Copy link
Author

peerem commented Mar 14, 2021

I found the problem. When debugging in Visual Studio, you do not copy the content files from third-party packages into the debug folder. You can also see this in the browser console:

Failed to load resource: net::ERR_NAME_NOT_RESOLVED https://app/_content/Blazored.Modal/blazored.modal.js

The published release version works without any problems. Everything is copied.

@MikeYeager
Copy link
Collaborator

Thanks for the post. Please join the discussion on #18

@ottodobretsberger ottodobretsberger added the bug Something isn't working label Mar 25, 2021
@ottodobretsberger
Copy link
Contributor

It appears that this might be an issue with Visual Studio settings, of the 3rd party library files not set to copy to the output folder.
We will add something about it to our FAQ section in our documentation, but we aren't sure we can add a blanket solution to this kind of issue that applies to all possible 3rd party libraries.

@peerem
Copy link
Author

peerem commented Apr 2, 2021

Did you read that?

The published release version works without any problems. Everything is copied.

This third party library was just an example and works in every other scenario (WASM, pure Server, Chromely) so I don't think it's a library problem!

@MikeYeager
Copy link
Collaborator

Thank you for the additional comments. We believe this is related to #20 which includes suggested work-arounds. Please continue the conversation there if you have additional comments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants