ABP 4.3.0 Blazor
In other Blazor server projects I have used the following technique to communicate between background servces and the pages
https://dzone.com/articles/blazor-how-tos-status-from-a-background-task
An alternate to this would be sockets but I would prefer to use
@code{
protected override void OnInitialized()
{
State.OnChangeAsync += Refresh;
}
private async Task Refresh()
{
await InvokeAsync(StateHasChanged);
}
public void Dispose()
{
State.OnChangeAsync -= Refresh;
}
}
Do you know iif this approach will work with Blazor WASM or should I fallback to traditional SignalR sockets
Many thanks in advance
J
ABP 4.3.3 Blazor WASM
We have a key client who host the ABP solution on Azure behind a proxy. Most urls are working correctly and set correctly in the IdentityServerClient tables. However Https:// ..... .well-known/openid-configuration is returning the forbidden URL of the Azure host rather than the poxy public facing address {"issuer":"https://restructed URL Behind the proxy ..... Rather than the correctly set URL in the database.
We are completely blocked from deploying because of this and looking at a short term hack of the identity server to get us live. It looks like the Identity server is using HttpContext.Request.Host rather than the database URL to set the URL values.
Do you have a simple way to override this with some kind of appsetings or DB setting.
Hope this makes sense, all other URLs are correct, just the Open ID ones are getting the server address behind the proxy rather than the public address.
Hi ABP gurus, starting from ABP Suite we generated a preview version with Blazor web assembly We have the latest visual studio 2022 preview with .net 6.0.100-rc.2.21505.57 The host starts fine but the browser hangs when running the web assembly We have tried debug and release modes running IIS and Kestrel but no luck. We get This Page Isn't Responding every time, whatever we do in both Edge and Chrome
We would love to get ahead of the curve and build our next soln in .net 6 but this is a blocker and I cant help thinking we are missing something obvious. (This has been tried on different machines by different developers with the same result)
