I am updating a div with a partial view by using something like this:
<% using (Ajax.BeginForm(\"Action\", \"Controller\",
new { id=Model.i
Any reason for not doing it the right way (after all we are in 2010)? Dump MS AJAX where it belongs along with all the Ajax.*
helpers which depend on it and write proper code. While using MS AJAX in classic webforms could have been justified because of the UpdatePanels, etc... doing it in a new ASP.NET MVC application today, especially after Microsoft have fully embraced jQuery, seems like a bad idea.
So after the rant here's my recommendation:
<% using (Html.BeginForm("Action", "Controller", new { id = Model.id }) { %>
and then attach the submit handler unobtrusively using jquery in a separate file:
$(function() {
$('form').submit(function() {
$.ajax({
url: this.action,
type: this.method,
success: function(result) {
// feel free to execute any code
// in the success callback
$('#result').html(result);
}
});
return false;
});
});
or using the excellent jquery form plugin:
$(function() {
$('form').ajaxForm(function(result) {
// feel free to execute any code
// in the success callback
$('#result').html(result);
});
});
Benefits of this approach:
Bonus benefit: no headaches.
I kept looking around and found the answer here:
Assign a Javascript function to AjaxOptions OnSuccess property raise an error - ASP.NET MVC (with the answer that was not selected)
Quoting Atzu
If you have to pass any parameter to the OnSuccess event you may have to write the funcion in this way.
OnSuccess = "function(){exampleFunction('" + param1 + "');}
and it worked for me!