-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
.net8+orchardcore blazorserver mode render component error #16363
Comments
This bug has been discussed before, but it has not been merged into the main branch yet. enable module; open /Hello |
Can you link to the issue that you mention? |
I won't solve this problem, it's a bit difficult for me, but it has been discussed before; I can only provide a method of reproduction, as I uploaded the module code for OrchardCore above; You can also take a look at the previous discussion records. reference bug #15211 |
It seems that this issue didn't really move for quite a while despite us asking the author for further feedback. Is this something you'd like to revisit any time soon or should we close? Please reply. |
I recorded a debugging video to illustrate the situation. 20240719_143215.mp4 |
We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues). This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here. |
Have you tried to invoke it from a tag helper as it was suggested in the other issues? #15211 (comment) |
Still reporting an error, the theme is using a style that includes liquid |
There may be an issue with the output of LiquidViewTemplate, but I don't know how to resolve it. |
Describe the bug
.net8+orchardcore create webpage, use blazorserver mode @(await Html.RenderComponentAsync(RenderMode.ServerPrerendered)) error.
error content:
System.InvalidOperationException: The current thread is not associated with the Dispatcher. Use InvokeAsync() to switch execution to the Dispatcher when triggering rendering or component state.
To Reproduce
Steps to reproduce the behavior:
Create a OrchardCore app, add module, and add WebPage page.
Create blazorclasslibrary project, add default Component.
call Html.RenderComponentAsync in webpage.
browser webpage.
Expected behavior
System.InvalidOperationException: The current thread is not associated with the Dispatcher. Use InvokeAsync() to switch execution to the Dispatcher when triggering rendering or component state.
Screenshots
reference bug #15211
The text was updated successfully, but these errors were encountered: