-
Notifications
You must be signed in to change notification settings - Fork 10k
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
Mixing Blazor WebAssembly and Blazor Server Pages in same application #37131
Comments
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process. |
Thanks for contacting us. Unfortunately, we still don't have a good story for this. |
I guess you could still do it somehow without the support from microsoft (using supported tools), by serving client side mono and letting user to interact with it, while signalR updating your dom rendered on the server |
Closing this since we're tracking this work as part of #38128. |
I happen to come across Q & A in old Blazor Presentation by Ryan Nowak
@ 45.55 second
https://youtu.be/SbFLKt8eSXk?t=2742
Is there any update on how to do that ? What would routing look like which could handle both the wasm and server scenario ?
In my Blazor Hosted wasm app, I have need to send URL in SMS to the user and user can click the URL,
but this time instead of loading entire Blazor WASM, I want a server side page to run and just render the HTML, instead of download the entire APP.
I think it is great idea to allow such functionality as maximum of the boiler plate code is already written on the server App and would prevent deploying the entire server app again as Blazor Server again on Azure APP service. This also introduces maintenance headaches.
The text was updated successfully, but these errors were encountered: