I want to be able to click a button, have a function in my controller return a JSON object that can be used on my page without the page reloading.
My controller:
//Dont know if HttpPost is right
[HttpPost]
public ActionResult GetPinPoints() {
return jsonobject;
}
I want to be able to call this and have it return a JSON object on a page in AJAX so I dont have to reload the page.
Two Parts:
1) The Controller
public JsonResult GetPinPoints()
{
var stuff = DoStuff();
return Json(stuff);
}
2) The View (via JQuery)
$('#SomeButtonId').click(function () {
$.ajax({
url: '/Controller/GetPinPoints',
type: "POST",
dataType: "json",
success: function(data) {
$('#someSuccessDiv').html(data).fadeIn();
//Do whatever here, just a poor mans example
},
error: function() {
$('#someErrorDiv').html('Boo').fadeIn();
}
});
return false;
});
contentType should describe the encoding format of the input parameters (jQuery's "data"). When you're working with ASP.NET WebForms' ScriptServices and PageMethods, you have to use JSON encoded data parameters and a content-type of application/json in order to coax JSON responses out of them. Working with ASP.NET MVC, you can use application/form-url-encoded parameters instead, which is more common, yet still respond with JSON.In .ajax, use post method to call this method:
[HttpPost]
public ActionResult GetPinPoints() {
var obj = new ...
return Json(obj);
}
The easiest way to do this is to use the protected Json method on the Controller class. This will take an object and return it's JSON representation using in a JsonResult.
Using your example:
public ActionResult GetPinPoints() {
return Json(jsonobject);
}
If you do not like the way that ASP.NET MVC serializes your object into JSON, you can do it yourself, creating an ActionResult which will take your object (or the JSON you build) and write the contents back to the response stream. Just make sure that the ContentType that you send back is of type application/json or text/javascript.
From there, you can use a call to getJSON in jQuery to get the results and then use the object however you wish.
Note that if you don't need anything overly complex, or your designs don't call for it, you do not need the HttpPostAttribute.