dotnet / dotnet/aspnetcore

Ability to run multiple Blazor server / Web assembly apps in the same document (micro-frontends)

Open
#38,128 46 comments 136 reactions 0 assignees View on GitHub
area-blazor enhancement needs-prototype Needs: Design Pillar: Complete Blazor Web Priority:1
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 10h
Merged PRs (30d)
281

Description

It's interesting for us to consider running Blazor Server and WebAssembly applications in the same document as well as being able to mix them on the same apps. We've heard feedback that some people don't want to have some "proprietary business logic" on the client, and this offers a way to to do so. In the same vein, we can expect larger apps developed by several teams to run into conflicts on the versions used by their apps. Being able to run multiple blazor versions on the document, avoids this problem at the cost of increased app size.

## UPDATE (from @MackinnonBuck)

> We've opened https://github.com/dotnet/aspnetcore/issues/48032 to track the ability to have a single Blazor app that uses Server and WebAssembly components on the same page. This enables scenarios critical to the https://github.com/dotnet/aspnetcore/issues/46636 effort. It does not, however, include the ability to have completely separate Blazor app instances exist on the same page. That remaining work is what this issue tracks.

Source: https://github.com/dotnet/aspnetcore/issues/38128#issuecomment-1559891706

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.