Skip to content

Micro FrontEnds with Blazor Server (No Web Assembly) #60672

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
1 task done
nssidhu opened this issue Feb 28, 2025 · 2 comments
Closed
1 task done

Micro FrontEnds with Blazor Server (No Web Assembly) #60672

nssidhu opened this issue Feb 28, 2025 · 2 comments
Labels
area-blazor Includes: Blazor, Razor Components ✔️ Resolution: Answered Resolved because the question asked by the original author has been answered. question Status: Resolved

Comments

@nssidhu
Copy link

nssidhu commented Feb 28, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

The #38128 issue is trying to cover too many aspects.

I created this to isolate a feature i think should be easy to implement and restricted to Blazor Server only.
Blazor is by default a component based architecture, hence i am requesting that we create a RemoteServerWebComponents , that just points to another Blazor server hosting that component. this would help build Micro-Frontends. Think of this Webcomponent or IFrame.

React is already providing such feature. i have seen where Blazor component can be exported as Custom HTML element. But in this case i am talking about making something simpler and first class citizen.

<RemoteServerWebComponents URL="" .... >

This would allow various component to be consumed from other Blazor app. This RemoteServerWebComponents should load all the .css/Javascript that is necessary to run that RemoteServerWebComponents . The host would whitelist on what cookies/authentication token will be sent to RemoteServerWebComponents Server.

Describe the solution you'd like

Most modern front ends now a days allows to create micro-front ends.
Allowing the already built application to be included as RemoteServerWebComponents , this would allow to re-use already developed app.

Additional context

No response

@dotnet-issue-labeler dotnet-issue-labeler bot added the area-blazor Includes: Blazor, Razor Components label Feb 28, 2025
@javiercn
Copy link
Member

javiercn commented Mar 3, 2025

@nssidhu thanks for contacting us.

This is not a direction we plan to take, the issue you referenced already covers improvements in this area. It's also unclear how what you are proposing differs from an iframe, which you should already be able to do. WRT to cross-origin blazor server apps, there's a lot of things that need to be taken into account, including lots of details on CORS and other cross-origin restrictions that are not being taken into account.

@javiercn javiercn added question ✔️ Resolution: Answered Resolved because the question asked by the original author has been answered. labels Mar 3, 2025
Copy link
Contributor

This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes.

See our Issue Management Policies for more information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-blazor Includes: Blazor, Razor Components ✔️ Resolution: Answered Resolved because the question asked by the original author has been answered. question Status: Resolved
Projects
None yet
Development

No branches or pull requests

2 participants