Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

CSLA 8 uses wrong IContextManager in aspnetcore when Blazor Server is also used #4182

Closed
rockfordlhotka opened this issue Aug 22, 2024 · 0 comments · Fixed by #4183
Closed

CSLA 8 uses wrong IContextManager in aspnetcore when Blazor Server is also used #4182

rockfordlhotka opened this issue Aug 22, 2024 · 0 comments · Fixed by #4183
Assignees
@rockfordlhotka
Labels
area/Blazor Blazor kind/bug

Comments

@rockfordlhotka
Copy link
Member

rockfordlhotka commented Aug 22, 2024 •
edited
Loading

If you have a Blazor 8 app that does the following:

  1. Is configured to use CSLA state management, so state is kept in sync between server and wasm, including user identity
  2. Is configured to not flow the user from the wasm client to the data portal server (this is the default)
  3. Makes a data portal call from a wasm client to the aspnetcore/Blazor server
  4. The data portal on the server makes another root data portal call (such as a UoW object)
  5. That second data portal call should be using the aspnetcore IContextManager, but it continues to use the state-aware Blazor context manager
  6. This fails, because the data portal attempts to call SetUser, thinking it is running in aspnetcore, but having the wrong context manager (Blazor server) which doesn't support setting the user

The fix is to ensure that, with a cascading root data portal call like this, that the correct context manager is used.

Probably related to #4075
@rockfordlhotka rockfordlhotka self-assigned this Aug 22, 2024
rockfordlhotka added a commit that referenced this issue Aug 23, 2024
@rockfordlhotka
#4182 Don't remove other context managers, b/c the accessor needs to …
70496df 
…scan them all
@rockfordlhotka rockfordlhotka mentioned this issue Aug 23, 2024
Merged
@rockfordlhotka rockfordlhotka linked a pull request Aug 23, 2024 that will close this issue
Fix issue with context manager in a Blazor server setting #4183
Merged
rockfordlhotka added a commit that referenced this issue Aug 23, 2024
@rockfordlhotka
Fix issue with context manager in a Blazor server setting (#4183)
a2f861e 
* Update to latest nuget packages

* Ensure use of .NET 8 b/c .NET 9 has a bug

* Update version numbers to 8.2.6

* Add context manager tests

* Make HttpContext fake function enough for testing

* #4182 Don't remove other context managers, b/c the accessor needs to scan them all

* Target latest .NET 8 SDK

* Update to target CSLA 8.2.6

* Update release notes
rockfordlhotka added a commit that referenced this issue Oct 1, 2024
@rockfordlhotka
#4182 Fix issue with Blazor context manager
5ebd9f9
@rockfordlhotka rockfordlhotka mentioned this issue Oct 1, 2024
Merged
rockfordlhotka added a commit that referenced this issue Oct 1, 2024
@rockfordlhotka
#4182 Fix Blazor context manager issue
9607d51
@rockfordlhotka rockfordlhotka mentioned this issue Oct 1, 2024
Merged
rockfordlhotka added a commit that referenced this issue Oct 2, 2024
@rockfordlhotka
#4182 Fix context manager accessor
c929053
rockfordlhotka added a commit that referenced this issue Oct 21, 2024
@rockfordlhotka
#4182 Fix issue with IContextManager selection
24aea28
rockfordlhotka added a commit that referenced this issue Oct 21, 2024
@rockfordlhotka
Fix Blazor context manager issue (#4239)
d1a2631 
* Update version to 8.2.7

* #4182 Fix issue with Blazor context manager

* Fix .NET target

* Update CSLA version
rockfordlhotka added a commit that referenced this issue Oct 21, 2024
@rockfordlhotka
Explore possible perf issues with static property loading (#4234)
e035ad7 
* If !SyncContextWithServer properly load empty session

* #2551 Updating ProjectTracker code

* #4182 Fix Blazor context manager issue

* Optimize code

* Fix issue where "non-mobile" objects don't serialize

Non-mobile objects now need to have an opportunity to be serialized by a custom formatter for that type, so all types should _try_ to serialize.

* Clarify test names

* #4182 Fix context manager accessor

* Update to latest CSLA

* #4182 Fix issue with IContextManager selection

* Provide better exception information
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rockfordlhotka rockfordlhotka

Labels
area/Blazor Blazor kind/bug
Projects
No open projects
CSLA Version 8.2.6
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix issue with context manager in a Blazor server setting MarimerLLC/csla
1 participant
@rockfordlhotka