InvalidOperationException after upgrading to CSLA 8 prerelease 24010305

[mtavares628]

@rockfordlhotka I have updated to the latest CSLA 8 prerelease, and am running into an issue that I can't figure out. Outside of updating the Nuget packages to prerelease 24010305, I also made the following change to program.cs from this:

    builder.Services.AddCsla(options => options
        .AddAspNetCore()
        .AddServerSideBlazor()
        .PropertyChangedMode(Csla.ApplicationContext.PropertyChangedModes.Windows)
        .DataPortal(dpo =>
        {
            dpo.RegisterDataPortalCache(typeof(NdrnCache));
        })

to this:

    builder.Services.AddCsla(options => options
        .AddAspNetCore()
        .AddServerSideBlazor()
        .DataPortal(dpo =>
        {
            dpo.ClientSideDataPortal(cdpo => cdpo.DataPortalCacheType = typeof(NdrnCache));
        })

When I run the application, I'm prompted to my Identity Server and can log in, but when I am redirected back to my Blazor Server app I end up with the following exception:

Error: System.InvalidOperationException: Headers are read-only, response has already started.

   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpHeaders.ThrowHeadersReadOnlyException()

   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpResponseHeaders.Microsoft.AspNetCore.Http.IHeaderDictionary.set_SetCookie(StringValues value)

   at Microsoft.AspNetCore.Http.ResponseCookies.Append(String key, String value)

   at Csla.Blazor.State.SessionIdManager.GetSessionId()

   at Csla.Blazor.State.SessionManager.GetSession()

   at Csla.AspNetCore.Blazor.ApplicationContextManagerBlazor.GetClientContext(ExecutionLocations executionLocation)

   at Csla.ApplicationContext.get_ClientContext()

   at Csla.ApplicationContext.get_RuleSet()

   at Csla.Rules.BusinessRules.HasPermission(ApplicationContext applicationContext, AuthorizationActions action, Type objectType, Object[] criteria)

   at Csla.DataPortal`1.DoFetchAsync(Type objectType, Object criteria, Boolean isSync)

   at Csla.DataPortal`1.FetchAsync(Object[] criteria)

   at Dad.Business.LastClientsViewedInfoCollection.GetLastClientsViewedInfoCollectionAsync(Int32 employeeID, Int32 advocacyGroupID, IDataPortalFactory factory) in D:\Users\mtavares\Source\repos\Dad\Dad.Business\Client\LastClientsViewedInfoCollection.Designer.cs:line 74

   at Dad.Ui.Blazor.Shared.TopMenu.RefreshMenu(EntityTypeIDs entityType) in D:\Users\mtavares\Source\repos\Dad\Dad.Ui.Blazor\Shared\TopMenu.razor.cs:line 126

   at Dad.Ui.Blazor.Shared.TopMenu.OnInitializedAsync() in D:\Users\mtavares\Source\repos\Dad\Dad.Ui.Blazor\Shared\TopMenu.razor.cs:line 155

   at Microsoft.AspNetCore.Components.ComponentBase.RunInitAndSetParametersAsync()

   at Dad.Ui.Blazor.Components.CustomComponentBase.InvokeWithBlazorServiceContext(Func`1 func) in D:\Users\mtavares\Source\repos\Dad\Dad.Ui.Blazor\Components\CustomComponentBase.cs:line 68

In wondering if the use of the cache had anything to do with the issue, I also removed that from the DataPortal options as well, but still ended up with the same issue.

I haven't upgraded to .NET 8 yet, and am running on .NET 7. Is there some other option that I need change in order to get this working in this CSLA version?

[rockfordlhotka]

The exception appears to be coming from the SessionIdManager, which is part of the new state management mechanism in Blazor.

The SessionIdManager creates and reads a cookie from the http request object off HttpContext.

What I get from the exception is that the id manager is attempting to append the cookie to the request object, and the request object is set to read-only by that time.

I think the solution is for your initial app landing page to inject an ISessionManager and call its InitializeAsync method in your landing page's OnInitializedAsync.

It might be possible to do this in the App.razor page in .NET 7. I don't think that'll work in .NET 8, though that's an interesting thought.

The one trick on the landing page (at least if it is a server-static page) is that you can't interact with the data portal or the local/client context objects on that page - this is because the cookie isn't actually written to the browser until the page has finished rendering.

You can look at the BlazorExample project to see how this is done.

I am thinking though, that perhaps the use of the state management should be opt-in. It is opt-in on wasm, but not on the server, and maybe it should be opt-in on the server too. If someone doesn't use local/client context in their app, there should be no need to have this feature at all.

[mtavares628]

@rockfordlhotka Upon further research, I think the errors are related to the new StateManager using TaskCompletionSource. A google search turned up this info:

The exception "System.InvalidOperationException" in Microsoft.AspNetCore.Components.Server.dll is thrown when the component is being statically rendered. This can happen when you're using a TaskCompletionSource and setting it to complete when it is already set to complete, or when you're doing some JsInterop calls on completed tasks.
Here are some things you can try to fix this issue:
Make sure that you're not using a TaskCompletionSource and setting it to complete when it is already set to complete.
Make sure that you're not doing any JsInterop calls on completed tasks.

I'm not sure how to troubleshoot this further, since I'm not that familiar with this new StateManager. Any guidance is appreciated.

[rockfordlhotka]

Logged as #3737

[rockfordlhotka]

@mtavares628 I did put the old Blazor 7 context manager back into CSLA to support pre-.NET 8 behavior - #3657

builder.Services.AddCsla(o=>o
.AddAspNetCore()
.AddServerSideBlazor(so => so.UseInMemoryApplicationContextManager = true));

[mtavares628]

@rockfordlhotka I had used that configuration in my testing of the latest pre-release:

    builder.Services.AddCsla(options => options
        .AddAspNetCore()
        .AddServerSideBlazor(bo =>
        {
            bo.UseInMemoryApplicationContextManager = true;
        })
        
        .DataPortal(dpo =>
        {
           dpo.ClientSideDataPortal(cdpo => cdpo.DataPortalCacheType = typeof(NdrnCache));
        })
        );

By using the the old Context manager, does it then bypass the State Manager altogether?

[rockfordlhotka]

Right - if you use the in memory context manager then you should not initialize or interact with the state management subsystem at all.