TagBuilder.MergeAttributes(new RouteValueDictionary(htmlAttributes)) TagBuilder.MergeAttribute("href", string.Format("javascript:document.submit() ", formName)) TagBuilder tagBuilder = new TagBuilder("a") Public static string SubmitLink(this HtmlHelper htmlHelper, string linkText, string formName, object htmlAttributes) The first argument is the link text and the second is the form name. You can see this allows us to have a consistent coding paradigm. An alternative for this scenario is to just create a simple SubmitLink HTML helper that will allow you're code to look like this: But what to do for the Save link given that we don't have anything in MVC out of the box that is analogous to the LinkButton in ASP.NET web forms? One solution might be to just use JavaScript like this:īut that is somewhat ugly and the paradigm is inconsistent with the Cancel button where we're using a normal ActionLink. The Cancel button is easy because we can just use a normal Hmtl.ActionLink helper to redirect to whatever our cancel page is. It might be visually more appealing/consistent or whatever your reason might be to have your buttons look like this:
Often when creating web applications, it's common for us to want to submit or post forms to the server by using a hyperlink rather than an HTML submit button.
0 kommentar(er)
