Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am torn between the idea of using Html.RenderAction vs. Html.RenderPartial for partial views. Using RenderPartial means manipulating and passing ViewModel, something I feel is cumbersome. RenderAction is neat and concise in this case but not included for RC1 (included with futures though).
Why is it so? Any specific reason?
As far as I remember they decided to move it to futures assembly because they want to release first version of the framework as soon as possible and there are some problems with RenderAction (here is an example). And RenderAction is planned to be included in asp.net mvc version 2. In my opinion it’s better to use SubController’s from MvcContrib instead of RenderAction.