-
Notifications
You must be signed in to change notification settings - Fork 65
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
Comments
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. |
Thanks for the post. Please join the discussion on #18 |
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. |
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! |
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. |
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
The text was updated successfully, but these errors were encountered: