stagep

@Rhywden When you add Fluxor to your services in the server project, the ScanAssemblies method has an overload that allows you to include additional assemblies so you can reference the...

One way to initialize the client side store is to add a component in your client project that contains ``` @rendermode InteractiveWebAssembly ``` and then add this component to your...

Please tell us what options you selected for Interactive render mode and Interactivity location when creating the project(s).

Do the components using Fluxor exist only in the Client (WebAssembly) project?

I have created a sample application that demonstrates Fluxor working in the client (WASM) successfully with a client counter. The application also includes a server side counter that does not...

@mrpmorris The example that I put on Github is using InteractiveServer and InteractiveWebAssembly rendering to represent a stateful application on both the server and the client. This example will only...

InteractiveServer render mode is not stateless. [ASP.NET Core Blazor state management](https://learn.microsoft.com/en-us/aspnet/core/blazor/state-management?view=aspnetcore-8.0&pivots=server)

@mrpmorris Did you have a chance to look at my stateful server and client application? It seems that the Fluxor library will only work with either InteractiveServer or InteractiveWebAssembly rendering.

I updated my sample. Counters on both Server and WebAssembly work. State will be lost on the Server counters once you switch to using only WebAssembly as the connection to...

You need to initialize the store. Add the following to the GetCustomer.razor page. ``` ```