All geek questions in one place

Html.RenderAction. Why is it not included in MVC RC1?

I am torn between the idea of ​​using Html.RenderAction vs. Html.RenderPartial for partial views. Using RenderPartial means manipulating and passing the ViewModel, something that I feel is cumbersome. RenderAction is neat and concise in this case, but not included in RC1 (including futures).

Why is that? Any specific reason?

+3
source share
3 answers

As far as I remember, they decided to transfer it to the assembly of futures, because they want to release the first version of the framework as soon as possible and there are some problems with RenderAction ( here is an example ). And it is planned to include RenderAction in asp.net mvc version 2. In my opinion, it is better to use SubController from MvcContrib instead of RenderAction.

+2
source

There are other unobvious obscure “problems,” such as the POST action that is invoked in the child control, as well as its parent element, when the child was rendered by RenderAction.

I made a post about this here .

, -, , , , , , .

RenderPartial, , POST.

+1

I do not know the reasons why he was moved (to "futures"); by assumption, make it less "obvious" because it has a higher cost than RenderPartial (simulating a lot more pipeline, etc.).

0
source

Source: https://habr.com/ru/post/1703639/

More articles:


All Articles