I need a form on my ASP.NET MVC Razor page. My preference would be to use the following syntax:
@using (Html.BeginForm())
{
}
However, I need several attributes added to the form. So I ended up with something like the following:
@using (Html.BeginForm(null, null, FormMethod.Post, new { name = "value" }))
{
}
However, this has an undesired side effect. If there are query arguments in this page’s request, the first form passes them along when the form is submitted. However, the second version does not.
I really don’t know why BeginForm() doesn’t support attributes, but is there a straight-forward way to add attributes to BeginForm() and still pass along any query arguments when the for is submitted?
EDIT:
After looking into this, it would seem the best solution is something like this:
<form action="@Request.RawUrl" method="post" name="value">
</form>
However, when using this syntax, client-side validation is disabled. It seems there is no good solution to this situation without more complicated and potentially unreliable constructs.
That’s indeed true, but I would go with a custom helper in order to preserve the form context inside which is used for client side validation:
which could be used like this: