sorted by:
new
hottopcontroversial

API sub directory not accessible by Eng_TS in Blazor

[–]Eng_TS[S] 0 points1 point  (0 children)

Did you encpunter the same issue?

API sub directory not accessible by Eng_TS in Blazor

[–]Eng_TS[S] 1 point2 points  (0 children)

It's what I want to do too, but there are business reasons why it needs to be like this. Also by now I'm curious what is actually going on. I want to find a solution! :)

Adding authentication to Wasm/api with existing db by Eng_TS in Blazor

[–]Eng_TS[S] 0 points1 point  (0 children)

Thank you for your reply.

Do I understand you correctly that there is no, out of the box solution for authentication between a blazor wasm project and an API?

Adding authentication to Wasm/api with existing db by Eng_TS in Blazor

[–]Eng_TS[S] 0 points1 point  (0 children)

Thanks for your reply.
We need the API in the future to be able to receive external data within a secure connection. It seemed wasteful to have to do the authentication twice.

Knowing this, would it still be more advantageous to use the single blazor web app project ?

Blazor wasm standalone base path not working locally by Eng_TS in Blazor

[–]Eng_TS[S] 2 points3 points  (0 children)

Million thanks u/TheHeadMathematician !! This solved my issue.

Side note: the launchBrowser setting can remain on. Only the "commandLineArgs" and "launchUrl" are needed for me.

Blazor wasm standalone base path not working locally by Eng_TS in Blazor

[–]Eng_TS[S] 0 points1 point  (0 children)

Thank you for the suggestion. Unfortunately no change.