Replies: 11 comments 9 replies
-
@qunshen I believe this is because Oqtane is setting StreamRendering in the Routes and Head component - which is necessary to get Static Blazor to render content (if the StreamRendering is removed the framework does not render any content). This issue has been logged with Microsoft - dotnet/aspnetcore#54157 and I am hopeful will be resolved eventually. In the meantime your observation is correct that Auto render mode does not work as intended - but we are still going to release 5.1 this week as all of the other render modes are functioning properly. |
Beta Was this translation helpful? Give feedback.
-
from my perpective, auto render mode is the most userful feature in real world application。 I also look into the default project template of Balzor WebApp and the auto render mode is functional as intended! Thanks! |
Beta Was this translation helpful? Give feedback.
-
It appears that auto render mode has something to do the routing! if you use "@page "/xxx"", it works as intended! |
Beta Was this translation helpful? Give feedback.
-
I have an ideal: can we simulate the "@page /xxx" by fall back all route to one page which has only one component--siterouter? this way,oqtance only has one page using "@page/" |
Beta Was this translation helpful? Give feedback.
-
this is at Server. if we can find a way to fallback to one page at client, we might able to using "@page" to specify router while to use Oqtane's dynamical nature. |
Beta Was this translation helpful? Give feedback.
-
Yes. but Oqtane doest not use ."@page". what I an suggeting is that if we can use "@page" to define one page and all dynamical generated pages fallback to the page at client side. this way ,Auto render mode might work. |
Beta Was this translation helpful? Give feedback.
-
ok! my point is that making oqtane a more "@page/" type application, while perserve its dynamcal nature! I will do some experiment! |
Beta Was this translation helpful? Give feedback.
-
Link to the Blazor default router which includes a comment:
|
Beta Was this translation helpful? Give feedback.
-
Hello everyone. Here is some more interesting behavior I have observed while in Interactive Client/Auto modes and not found in any static mode from the HTML Module itself and changing pages. While in Interactive Mode with Client or Auto modes selected when you change from the homepage which has the shared secured content component also to the Private page which has this same component, the content loaded you can see get refreshed which maybe a clue. I believe changing render modes from server to web assembly and back again is not supported, once an interactive type has been selected I believe everything after that part of the component should inherit it. This behavior is not experience in server or any static modes. For example if you set the HTML module component override to Interactive.Server and the app is running its component wrapper as Interactive.Client or Interactive.Auto there might be a boundary issue here we might be crossing causing an issue as well potentially? |
Beta Was this translation helpful? Give feedback.
-
@qunshen I noticed in the asp.net repo on GitHub that there were a number of major bugs with Auto render mode in the initial .NET 8 release. You should install .NET SDK 8.0.4 in your environment to see if it resolves your earlier Auto render mode issue. |
Beta Was this translation helpful? Give feedback.
-
it appears works! |
Beta Was this translation helpful? Give feedback.
-
I played with Oqtane5.1 , and found that when you set InteractiveAutoRenderMode render model in site setting, the wholw site runs the same way as Webassembly mode. the UI displays only after runtime downloaded. with InteractiveAutoRenderMode ,the UI are supposed tp display quickly when connects to server before the runtime downloaded!
Beta Was this translation helpful? Give feedback.
All reactions