Skip to content

Render a webassembly component into the page #46354

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

Closed
mkArtakMSFT opened this issue Jan 31, 2023 · 2 comments · Fixed by #48664
Closed

Render a webassembly component into the page #46354

mkArtakMSFT opened this issue Jan 31, 2023 · 2 comments · Fixed by #48664
Assignees
Labels
area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-full-stack-web-ui Full stack web UI with Blazor Priority:1 Work that is critical for the release, but we could probably ship without
Milestone

Comments

@mkArtakMSFT
Copy link
Contributor

mkArtakMSFT commented Jan 31, 2023

#46704 describes the general approaches.

The work in this issue covers creating a handler that can be passed in to the HtmlRenderer we plan to provide inside Microsoft.AspNetCore.Components.Web and registering it in DI to handle webassembly components.

We also need to register the Blazor Webassembly endpoints on to the page inside the ComponentEndpointsDataSource

@mkArtakMSFT mkArtakMSFT added area-blazor Includes: Blazor, Razor Components feature-full-stack-web-ui Full stack web UI with Blazor labels Jan 31, 2023
@mkArtakMSFT mkArtakMSFT added this to the 8.0-preview2 milestone Jan 31, 2023
@mkArtakMSFT mkArtakMSFT added enhancement This issue represents an ask for new feature or an enhancement to an existing one Priority:1 Work that is critical for the release, but we could probably ship without labels Jan 31, 2023
@ghost
Copy link

ghost commented Mar 3, 2023

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@SteveSandersonMS
Copy link
Member

When implementing this, make sure RazorComponentResultExecutor is updated to support it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-full-stack-web-ui Full stack web UI with Blazor Priority:1 Work that is critical for the release, but we could probably ship without
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants