This is one of method inside my controller.
[HttpPost]
public JsonResult Ajax(string AJAXParameter1)
{
List<string> data = new List<string>();
data.Add("AJAXParameter1=" + AJAXParameter1);
return Json(new { data, result = "OK" });
}
If parameter AJAXParameter1 recieves value as passport i want to display view that contains fileds related to passport. If it recieves value as pan i want to render some different view that allow us to add pan card related details. For pan and passport i have models. Based on Id i want to generate view.
I believe the best way to do this is to simply create two views or partialviews based on how your application will have to look, one for the passport and one for the pan card.
Then in your controller method see which one you receive and return the view needed.
something like:
[HttpPost] public ActionResult ReturnNeeded(string Parameter1){
if (IsPassport(Parameter1)){
return View("PasswordView");
}else if (IsPan(Parameter1)){
return View("PanView");
}
return View("OopsBadRequest");
}
maybe?
Related
Hi have a scenario where in i have 3 views in the first view i have some textbox and then next button on click of next button the second view will be shown and the second view will also have some textbox and next button the third view is the final view which has few textboxes and submit/finish button. On click of submit/finish button all the data from view1,view2 and view3 should be saved to database. How to achieved it using ASP.NET MVC
You can use temp-data and their keep method to persist data in subsequent request.
Just keep all required field data into temp-data and get all this in one object(temp-data) and save them
Here is an eg. for it:
public ActionResult Add(Model model)
{
if(ModelState.IsValid)
{
db.Model.Add(model);
db.SaveChanges();
return RedirectToAction("Add2");
}
return View(model);
}
it redirects to the second view or a partial view, and the same with the 2nd to the 3rd. Hope it helps.
if you want to pass data from one view to another view then you can use TempData
ex.
TempData["Key"] = "test";
and can get value from tempdata like
#{
var abc = TempData["Key"];
}
Note: You can get tempdata value to next action after that it will be destroy.
In ASP MVC 4, is it possible from a view to call another controller action?
I'm on http://localhost:57456/Archers and I would like to call a method from the controller Participe (So should be http://localhost:xxxxx/Participe/Action).
This is only applying to this action, so I don't want to redirect every action to this controller.
You can use Html.Action inside your view to call child actions
<div> #Html.Action("Action","Participate") </div>
I would suggest you call your ParticipeController from the first action, and include the controller result into the view Data or the model to return to the view:
public class ArchersController {
public ActionResult Index() {
// your current code here
// your custom call
var result = new ParticipeController().Action("your params here");
ViewData["ParticipeResult"] = result;
// return View();
}
}
Maybe though, some responsibility principles could be applied here in order to isolate the Participe call you want to make here into its own class or method.
Say the requirement is to redirect to another page after successfully saving a model in an ASP.NET MVC controller:
[HttpPost]
public ActionResult Index(ViewModel viewModel)
{
if (ModelState.IsValid)
{
// Do save;
return RedirectToAction("whatever"); // <--- here's the problem
}
// display validation errors and so
return View(viewModel);
}
This would work fine unless the controller was rendered as a Child Action:
#{
Layout = "my layout";
Html.RenderAction("something else, a view for example");
Html.RenderAction("Index action of the above controller"); // <----
}
In this case RedirectResult class would check and see that the context is a child action and would throw the exception: "Child actions are not allowed to perform redirect actions".
I understand that writing to Response stream is already in progress and a redirect cannot take place here but nevertheless one has to be able to redirect to other pages after a server-side action in a controller even if that action is a child action. We use Layouts and RenderActions to reuse the shared parts of the page design.
How would you implement such a redirect in such a controller?
Edit:
The main goal is to reuse View/Controllers that do a specific job and split them to logical concepts like displaying some data or providing an edit form. My approach here is to use RenderAction to render their result into a container. Container view (main page's Index action) acts as a traditional asp.net Page, its Layout view as a Master page and edit and view controller/views are equivalent to User Controls (modules). The problem is there is no way to Redirect the Response after something has been written to it:
I'll submit a new answer in an attempt to keep things clean.
A normal mvc flow goes like this :
Http command reaches 1 controller which acts as a choirmaster(aka controller) and calls several logic containers(e.g services / commandHandlers) :
public ActionResult Index(){
var data = _yourService.FetchData();
return View(data);
}
This controller renders 1 view which can have multiple partials
#{
Layout = "my layout";
}
<p>Some html</p>
Html.RenderPartial("A shared partial");
Html.RenderPartial("shared\yourUserControl", Model.PropertyOrSomething);
If the partial contains too much logic to generate you could add a RenderAction or create an htmlHelper extension.
But neither of these should be able to control the flow of your request, a save or something that can redirect should in my opinion never be called from inside a view.
I assume you want to reuse the code in your controller so badly because it is getting quite big.
My advice would be to try and clear that controller up as much as possible by delegating as much of the logic upwards as you can.
Just by looking at your controller method for 5 seconds you should get an idea of what this action will do, if that's not the case : refactor it ! :)
If i understand correctly you have a parent controller which accepts a saveAction and while rendering the view you call another(?) saveAction as a child.
This flow feels unnatural to me. The parent action and only the parent action should handle the save command. You can render as many child actions as you want as long as they are only used to render some html(as this is what the view does). Don't let them handle redirection or saving, that way of working is everything but transparant for colleges or future you.
The controller controls the flow, not the view.
Edit:
A normal setup would be having 2 actions, eg: Index and Put.
public ActionResult Index(){
//fill model with dropdown data etc
return View();
}
public ActionResult Put(viewModel data){
if (ModelState.IsValid)
{
// Do save;
return RedirectToAction("whatever"); // <--- here's the problem
}
// display validation errors and so
return View("Index",viewModel);
}
Edit2:
If you return View("Index",viewModel) you will generate your index view with it's layout and the validation messages will be located in the modelstate.
Your view however should only have 1 childaction(or more if there are multiple, as long as it's not the save action).
Your Index view could look like this :
#{
Layout = "my layout";
}
Html.RenderAction("something else, a view for example");
#Html.BeginForm("Put","YourController"){
//all your input controls which will also show the validation errors
}
Edit 3:
If you want to reuse html code you should use #Html.Partial or Html helper extension methods. Note that if you pass no model the parents model is passed but you can pass a submodel to match the type safety of the partial.
It would look something like this :
#{
Layout = "my layout";
}
Html.RenderAction("something else, a view for example");
Html.RenderPartial("shared\yourUserControl", Model.PropertyOrSomething);
Try using AJAX in your view to do this, and instead of returning a RedirectToAction in your controller, return a JSON object:
View:
$.ajax({
url: '<%: Html.ResolveUrl("~/ControllerFolder/ControllerName/") %>',
type: "POST",
data: data,
success: function (result) {
$("#Div").html(result);
if (result.redirectUrl != null)
{
window.location = result.redirectUrl;
}
}
});
Controller:
[HttpPost]
public ActionResult Index(ViewModel viewModel)
{
if (ModelState.IsValid)
{
// Do save;
return Json(new { redirectUrl = Url.Action("NewAction", "NewController", RouteValues)});
}
// display validation errors and so
return View(viewModel);
}
Hope this helps...
It's really easy to return a different View from the Controller:
return View("../Home/Info");
However, I need a model in the Info view. I have a lot of stuff going on in the Info() action result method. I can just copy it and have something like this:
var infoModel = new InfoModel {
// ... a lot of copied code here
}
return View("../Home/Info", infoModel);
But that is not reasonable.
Of course I can just redirect:
return RedirecToAction("Info");
But this way the URL will change. I don't want to change the URL. That's very important.
You can call right to another action from within an action, like this:
public ActionResult MyAction(){
if(somethingOrAnother){
return MyOtherAction();
}
return View();
}
//"WhichEverViewYouNeed" is required here since you are returning this view from another action
//if you don't specify it, it would return the original action's view
public ActionResult MyOtherAction(){
return View("WhichEverViewYouNeed", new InfoModel{...});
}
It looks like you want to invoke an action from a different controller. I'd suggest that you might want to simply render a view that renders that action using Html.Action() instead of trying to tie the two together in the controller. If that's unreasonable then you might want to create a base controller that both controllers can derive from and put the shared code to generate the model in base controller. Reuse the view as needed.
public ActionResult Foo()
{
return View();
}
Foo View
#Html.Action( "info", "home" )
Why not just invoke the method of the action?
I have a problem with my data binding from View to Controller
I have an object that includes 3 other objects that I want to pass from controller to view
ModelView { Product, PagingInfo, Filter }
So this is how it looks like from controller
public ViewResult List(ModelView mv, int page = 1) {
var viewModel = new ModelView() { ... }
return View(viewModel);
and the View looks like this
Inherit = "viewModel"
using(html.BeginForm()) { Html.EditorFor(x => x.Filter.Name) ... }
Questions are:
Am i right for binding ModelView as a parameter in the controller? or should I bind Filter instead?
When I used a debugger, it seemed like whatever I put in textfield (Html.editorfor) doesn't get binded back the controller
Please Help
Thanks
My bad! It was working the entire time, I totally forgot that I put the default value as null in the routing system.
Sorry for the trouble :(