View Component Class and Umbraco 9 Surface Control
I often using Html.RenderAction in my projects based on Umbraco 8.
In particular, for client Ajax rendering, like searching and paging of records.
I implemented the MVC paradigma based on SurfaceControl functionalities and performing the action using Ajax.BeginForm helper method.
Now, starting a new Umbraco project I decided to test on field Umbraco 9. I supect that my ASP.NET MVC Widget was broken.
Infact, as we know, Html.RenderAction is nowhere to be found in .NET Core, so, I replaced the RenderAction with new View Components approach, which seams be the only way. This new approach exclude my surface control in a couple of round trip and as result the rendering of my (ajax) partial is showed as full page with URL similar to /surface/mycontroller/action
View Component Class and Umbraco 9 Surface Control
I often using Html.RenderAction in my projects based on Umbraco 8. In particular, for client Ajax rendering, like searching and paging of records. I implemented the MVC paradigma based on SurfaceControl functionalities and performing the action using Ajax.BeginForm helper method. Now, starting a new Umbraco project I decided to test on field Umbraco 9. I supect that my ASP.NET MVC Widget was broken.
Infact, as we know, Html.RenderAction is nowhere to be found in .NET Core, so, I replaced the RenderAction with new View Components approach, which seams be the only way. This new approach exclude my surface control in a couple of round trip and as result the rendering of my (ajax) partial is showed as full page with URL similar to /surface/mycontroller/action
Has anyone had a similarity experience?
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.