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.
As the subject says, is this a bad idea? If so, why?
Currently, if you are rendering some input fields from inside a @Html.Acion, the validation errors don’t get displayed to the user as the ModelState gets cleared when the @Html.Action gets involved (in its context.)
So whats the best pattern around it?
You can access the parent contexts via
ControllerContext.ParentActionViewContextorViewContext.ParentActionViewContext(details here) but I think there are better solutions.A child action is a good choice when you do not want to pollute all of your view models with data which are available independent from the current controller action and view (for example a user welcome label, a navigation bar, etc.).
For other reuse scenarios like common input fields a partial view is a better approach.
However if you give more details about your current scenario I try to suggest a more specific solution.