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.

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

Upgrade and test NET6 #32

Open
arivera12 opened this issue Dec 5, 2021 · 2 comments
Open

Upgrade and test NET6 #32

arivera12 opened this issue Dec 5, 2021 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@arivera12
Copy link
Owner

Hello @arivera12, I'd recommend skipping .NET 5 and going straight to .NET 6 in this case as .NET 6 has significant improvements to the byte array interop mechanisms.

Blazor no longer Base64 encodes/decodes byte[], and also natively supports streaming via JSStreamReference/DotNetStreamReference. This'll provide SIGNIFICANT improvements to stability and performance over .NET 5 in this area.

Links:

Originally posted by @TanayParikh in #28 (comment)

@arivera12
Copy link
Owner Author

Notes:

When passing a byte[] from .NET to JavaScript, the bytes are now received as a Uint8Array instead of as a Base64 encoded string. Code that previously decoded the Base64 encoded string will need to be removed. See the related announcement for details on this breaking change.

@arivera12
Copy link
Owner Author

I am missing here the stream management support which will be a huge improvement to add.

What I did to keep backward compatibility with older blazor apps was just adjust the JavaScript part to manage how blazor is transferring the data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant