Mackinnon Buck
Mackinnon Buck
@Lukespacewalker are you still experiencing this issue? If so, would you please be able to provide a repro project for us, hosted as a public GitHub repository?
@Lukespacewalker Thanks for providing a repro project! I've tried to reproduce the issue you're facing on both my local machine and a fresh VM, neither of which have had any...
@Lukespacewalker Fantastic, thanks for trying that out! Closing this out now.
I'm guessing that this error is happening because the HTML being loaded in the WebView sets a base href with an origin that's different from the document's location. This is...
Closing this out since this isn't a change we're going to make. See https://github.com/rrelyea/vscode-webview-blazor/pull/1 for an example of how to make Blazor WebAssembly work in a VSCode WebView and support...
@Perustaja, running `dotnet` on the published DLL should be sufficient. Navigating to the app's URL shouldn't result in a 404. Are you getting some other error in the application output?
@Perustaja The working directory of the application is determined by the directory where the `dotnet` command is executed, not the directory of its DLL. In this case, the `dotnet` command...
Sounds good, thanks. By the way, it might be best to document the practical aspect of this, not the technical details. My explanation above was the technical reason why the...
Hi @ltemimi, would you please provide a public, minimal repro project hosted as a GitHub repository that demonstrates the problem? Thanks!
Another thing you could try is checking if the default error boundary works correctly.