Replies: 3 comments
-
I assume you're talking about the Edit UIs etc. This is certainly not planned ;) The C# Blazor model has a LOT of drawbacks - and changing it would make 2sxc incompatible with DNN. IMHO Blazor is the next evolution of Razor, in terms of the component-model. But many other things it introduced - such as running .net in the browser - are IMHO not a good idea. The .net-in-browser appealed to C# developers who were afraid to learn JS SPAs. The new "Static Rendering" which was introduced in .net 8 is a clear indication that Microsoft also found it's way "back" :) |
Beta Was this translation helpful? Give feedback.
-
Not just about the edit UIs, but app development itself. Using both DNN and Oqtane, there are a couple issues preventing app creation for both CMSs:
|
Beta Was this translation helpful? Give feedback.
-
So the road forward IMHO is clearly Blazor on the server. The component model allows building things which are quite nice. Once Server-Side is really "cemented" we can look into providing Blazor as an optional renderer (in addition to Razor). |
Beta Was this translation helpful? Give feedback.
-
Hey.
Does 2sxc plan to support Oqtane's SPA framework and interactive mode to discard javascript for C#?
Or does it already?
Beta Was this translation helpful? Give feedback.
All reactions