You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My team is currently working on a framework that allows independent teams to build and deploy components which can be composed at runtime on a single page within an app. Each component renders in an iFrame. The goal of this is that each component is independently developed and built with its own release cadence, which avoids the need for a monolithic release cycle for the whole app.
At the moment this platform supports React components, but we're interested in using Blazor components within it too. However, there is a concern that if every widget renders independently, a page with (say) five components could end up loading and running 5 copies of the WASM .Net CLR into the browser - with the associated download speed, startup time and execution overhead.
Is there any way to share them? Obviously, we'd have to align the components built and deployed on the same .Net version (e.g., all components would need to be, say, .Net 8), but wondering if it's possible to load a single CLR runtime instance and have it shared by all components even if they're running within individual iFrames?
This would be for statically-deployed Blazor WASM components; we don't currently have plans to use Hosted Blazor WASM in this scenario - but might do in future (although I don't think it technically makes that much difference).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
My team is currently working on a framework that allows independent teams to build and deploy components which can be composed at runtime on a single page within an app. Each component renders in an iFrame. The goal of this is that each component is independently developed and built with its own release cadence, which avoids the need for a monolithic release cycle for the whole app.
At the moment this platform supports React components, but we're interested in using Blazor components within it too. However, there is a concern that if every widget renders independently, a page with (say) five components could end up loading and running 5 copies of the WASM .Net CLR into the browser - with the associated download speed, startup time and execution overhead.
Is there any way to share them? Obviously, we'd have to align the components built and deployed on the same .Net version (e.g., all components would need to be, say, .Net 8), but wondering if it's possible to load a single CLR runtime instance and have it shared by all components even if they're running within individual iFrames?
This would be for statically-deployed Blazor WASM components; we don't currently have plans to use Hosted Blazor WASM in this scenario - but might do in future (although I don't think it technically makes that much difference).
Beta Was this translation helpful? Give feedback.
All reactions