Replies: 3 comments
-
Excellent work @agriffard , totally agree with the WASM point, I am having a bit of a problem with the websocket connection that it has to maintain for the Blazor Server, to a point that we are abandoning Blazor and evaluating a strategy to port the current applications to a more traditional frontend. |
Beta Was this translation helpful? Give feedback.
-
Please have a look at PR #14961. IMHO it should be moved to OC.Samples As part of Orchard Core Contrib, I need to finalize something in my hand, and then I can publish a few samples, including Traditional CMS, Decoupled CMS, and Headless. Luckily, yesterday I was working on a Blazor Hybrid App. I will do an OC integration in the upcoming days Such samples need to be linked in our docs |
Beta Was this translation helpful? Give feedback.
-
Before I forget, @agriffard, we need to merge the Blazor sample that's included in the docs https://github.com/OrchardCMS/OrchardCore.Samples/pulls |
Beta Was this translation helpful? Give feedback.
-
As Aspire seems to become more and more important in the dotnet ecosystem, it would be interesting to give examples using Aspire and Orchard Core.
I saw that @MikeAlhayek was using it in his CrestApps.OrchardCore repo: https://github.com/CrestApps/CrestApps.OrchardCore/tree/main/src/Startup
Here is an example that I made with OC used as Headless api and a Blazor web app as Client to get the content of the pages : https://github.com/agriffard/Mochi
The scenario could be more simple with a Blazor WASM consuming data from OC.
Beta Was this translation helpful? Give feedback.
All reactions