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

Blazor AOT WASM Compilation #13690

Closed
legistek opened this issue Sep 4, 2019 · 2 comments
Closed

Blazor AOT WASM Compilation #13690

legistek opened this issue Sep 4, 2019 · 2 comments
Labels
area-blazor Includes: Blazor, Razor Components feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly ✔️ Resolution: Duplicate Resolved as a duplicate of another issue

Comments

@legistek
Copy link

legistek commented Sep 4, 2019

I hope I'm not duplicating an existing issue but I couldn't find any standing open issue on this.

Where do things stand with client-side Blazor and ahead of time (AOT) compilation to WASM? I feel like this has not been mentioned by anyone in a very long time. Is it even in the roadmap?

Blazor server-hosted (SignalR) performance is very good, but client-side is still unacceptable unfortunately.

Thanks for any info.

@mkArtakMSFT mkArtakMSFT added area-blazor Includes: Blazor, Razor Components feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly labels Sep 4, 2019
@mkArtakMSFT
Copy link
Member

Thanks for contacting us.
This is actually something we do track #5466

@mkArtakMSFT mkArtakMSFT added the ✔️ Resolution: Duplicate Resolved as a duplicate of another issue label Sep 4, 2019
@legistek
Copy link
Author

legistek commented Sep 4, 2019

Sorry, I don't know how I missed that! Thank you

@ghost ghost locked as resolved and limited conversation to collaborators Dec 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly ✔️ Resolution: Duplicate Resolved as a duplicate of another issue
Projects
None yet
Development

No branches or pull requests

2 participants