You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When adding a blazor wasm project, aspire will open both the aspire page in 1 browser, and another browser for blazor with wasm debugging support.
However, the port used for the wasm is the randomly generated REAL port https://localhost:50188/, rather than the url from launchSettings.json: https://localhost:7012/.
This makes it impossible to use something like openid authentication that requires a fixed port.
Expected Behavior
the proxy port is used
Steps To Reproduce
create new aspire project, add wasm project, add a counter, set breakpoint in incrementcount.
Launch browser on PROXY url, visit counter page -> no breakpoint
Launch browser on REAL url, visit counter page -> breakpoint ok
Exceptions (if any)
No response
.NET Version info
9.0.100
Anything else?
workaround: add this to aspire project definition:
.WithEndpoint("https", o=>o.IsProxied=false)
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Describe the bug
When adding a blazor wasm project, aspire will open both the aspire page in 1 browser, and another browser for blazor with wasm debugging support.
However, the port used for the wasm is the randomly generated REAL port
https://localhost:50188/
, rather than the url fromlaunchSettings.json
:https://localhost:7012/
.This makes it impossible to use something like openid authentication that requires a fixed port.
Expected Behavior
the proxy port is used
Steps To Reproduce
create new aspire project, add wasm project, add a
counter
, set breakpoint inincrementcount
.Launch browser on PROXY url, visit counter page -> no breakpoint
Launch browser on REAL url, visit counter page -> breakpoint ok
Exceptions (if any)
No response
.NET Version info
9.0.100
Anything else?
workaround: add this to aspire project definition:
The text was updated successfully, but these errors were encountered: