You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe the problem.
No response
Describe the solution you'd like
As you look at .NET 10 and the ability to store and restore application state if the circuit goes away, please keep in mind that not all data can be serialized via JSON.
Or to be more specific, you can serialize everything via JSON, as long as we have a hook to serialize our data into a byte[] or string that you can then put into the JSON.
In my case, I'm maintaining https://github.com/marimerllc/csla, which has its own serialization tooling. It is easy enough to convert CSLA state into a byte stream or even a string, but we'd need the Blazor API to allow us (or the app developer) to have the opportunity to use our serializer first to get the app state into a form where JSON is an option.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
No response
Describe the solution you'd like
As you look at .NET 10 and the ability to store and restore application state if the circuit goes away, please keep in mind that not all data can be serialized via JSON.
Or to be more specific, you can serialize everything via JSON, as long as we have a hook to serialize our data into a
byte[]
orstring
that you can then put into the JSON.In my case, I'm maintaining https://github.com/marimerllc/csla, which has its own serialization tooling. It is easy enough to convert CSLA state into a byte stream or even a string, but we'd need the Blazor API to allow us (or the app developer) to have the opportunity to use our serializer first to get the app state into a form where JSON is an option.
Additional context
No response
The text was updated successfully, but these errors were encountered: