blazor-server-side

问题 I know that calling the StateHasChanged() method notifies the component that the state has changed and that it should re-render. However, I also see calls to await InvokeAsync(StateHasChanged) or await InvokeAsync(() => StateHasChanged()) in other people's code, but I don't quite understand how it compares to StateHasChanged() and when should one be favored over the other, and why . The only information I could find was this part of the Blazor docs, it says: In the event a component must be

问题 I am trying to implement a basic custom Auth provider in my server side blazor project, but I am having some difficulty implementing the 'IsAuthenticating' property correctly. I used this site as my starter point, but it throws an error if ' IsAuthenticating ' is set to true (more specifically when I return null from GetAuthenticationStateAsync() ). https://gunnarpeipman.com/client-side-blazor-authorizeview/. Specifically this line of code: if(IsAuthenticating) { return null; <---- This line

问题 I am trying to implement a basic custom Auth provider in my server side blazor project, but I am having some difficulty implementing the 'IsAuthenticating' property correctly. I used this site as my starter point, but it throws an error if ' IsAuthenticating ' is set to true (more specifically when I return null from GetAuthenticationStateAsync() ). https://gunnarpeipman.com/client-side-blazor-authorizeview/. Specifically this line of code: if(IsAuthenticating) { return null; <---- This line

问题 I am trying to implement a basic custom Auth provider in my server side blazor project, but I am having some difficulty implementing the 'IsAuthenticating' property correctly. I used this site as my starter point, but it throws an error if ' IsAuthenticating ' is set to true (more specifically when I return null from GetAuthenticationStateAsync() ). https://gunnarpeipman.com/client-side-blazor-authorizeview/. Specifically this line of code: if(IsAuthenticating) { return null; <---- This line

问题 I am getting started with Blazor server-side and I don't get the routing right. I don't understand the need for the base tag in _host.cshtml . If I still have to add the base url in every Blazor component, for example: I want to have a base address of /app/ and the @page directive for the example Counter with a value of "/counter" does not "compile" to "/app/counter" . I have to set the @page to "/app/counter" which makes sense but that means that the base Tag in _host.cshtml is useless...

问题 I'm currently writing a (Server side) Blazor application that includes the default AzureAD Authentication. This works well for authenticated users - challenging on the entrance ( _Host.cshtml ) file, redirecting and then back once authenticated. I need to have a couple of pages not requiring authentication - I don't want the user being challenged and redirected to Microsoft. What is the correct way to do this? I have experimented with the AllowAnonymousAttribute , the AllowAnonymousToPage

问题 I'm currently writing a (Server side) Blazor application that includes the default AzureAD Authentication. This works well for authenticated users - challenging on the entrance ( _Host.cshtml ) file, redirecting and then back once authenticated. I need to have a couple of pages not requiring authentication - I don't want the user being challenged and redirected to Microsoft. What is the correct way to do this? I have experimented with the AllowAnonymousAttribute , the AllowAnonymousToPage

问题 I have a Blazer Server app which now uses authentication from a local ADFS server. Having identified the user, I now need to load their permissions. We don't think this can be provided via claims from the ADFS server, so want to configure this in the DB, but need to understand how/when to get this information. Regarding the hook into ADFS, my code is as follows (any suggestions on improvement most welcome) App.razor <CascadingAuthenticationState> <Router AppAssembly="@typeof(Program).Assembly

问题 I am a new user struggling to close a secondary signalR client gracefully from an ASP.NET Core Blazor Server Page. I am setting up a secondary signalR client connection on first render of a Blazor Server Page. I am trying to close this secondary signalR client connection when the Page is closed via the browser tab. At the time of writing DisposeAsync does not seem to be triggered when the page is closed via the browser tab. However, the Dispose method IS triggered. Furthermore in Safari 13.0

问题 I am a new user struggling to close a secondary signalR client gracefully from an ASP.NET Core Blazor Server Page. I am setting up a secondary signalR client connection on first render of a Blazor Server Page. I am trying to close this secondary signalR client connection when the Page is closed via the browser tab. At the time of writing DisposeAsync does not seem to be triggered when the page is closed via the browser tab. However, the Dispose method IS triggered. Furthermore in Safari 13.0