MVC Passing value from view page to controller : The Official Microsoft ASP.NET Forums

Mahesh108

<%

using (Html.BeginForm())<div>

{%><uc1:MenuControl ID="MnuCrtl" runat="server" value="" />

</div> <%} %>

In Controller

public ActionResult Report(FormCollection oformCollection) {}

I dont think this will work fine in MVC, if you want a treeview, you can look at this sample:

http://mvctreeview.codeplex.com/

Hope this helpful
Regards

Please mark the replies as answers if they help or unmark if not.
Feedback to us

Develop and promote your apps in Windows Store

Marked as answer by Young Yang - MSFT on Nov 12, 2012 01:00 AM

Reply

Re: MVC Passing value from view page to controller

Nov 06, 2012 07:06 AM|LINK

http://stackoverflow.com/questions/3507651/passing-values-between-view-and-controller-in-mvc-2

Let's ignore the "AJAX-y" aspects for a moment (because that's a different issue) and just look at passing data between views and controllers. I would first recommend that you check out the NerdDinner Tutorialwhich provides some good insights into how MVC works and how you use some of the features of MVC.

To address your specific question of how data is passed from View to Controller and back, there are a few ways to do this. However, the one that tends to make sense to most people is the idea of using strongly-typed views.

Let's say you have a model called Person. For now, don't worry about how we store Person data - we just have a Person class in the Models folder inside your MVC project.

public class Person { public string FirstName; public string LastName; public Person() { FirstName = "John"; LastName = "Doe"; } }

When we want to display data about Person in a View, we make a request to a specific controller. In this case (and for clarity) we'll call this controller the MainController. This will go in the Controllers folder and will be called MainController. Let's call the Action (an action is really just a specialized method) we want to get data from Index. Due to how ASP.NET MVC routing works, the path to our server will be:http://localhost/Main/Index. Notice the Controller (minus the "Controller" name), and the Action make up the path. (The first part is your server name, of course.)

Let's look at your controller - I'm going to keep it very simple for now:

public class MainController : Controller { public ActionResult Index() { Person person = new Person(); return View(person); } }

What we have going on inside the Index Action is that it is returning a View (which, by default, has the same name as the Action) and a model to correspond with that view. Now, we have to create our view.

The important part here is that you want to strongly-type the model that is being returned in the controller to your view. You do that with this line (which is first in your aspx file).

<%@ Page Title="" Language="C#" MasterPageFile="~/Views/Shared/Site.Master" Inherits="System.Web.Mvc.ViewUserControl<Project.Namespace.Person>" %>

Notice the "Inherits" attribute and notice that your Person model makes up that attribute.

Now, just code the rest of your view as normal. Let's say we want to display the current Person name, and allow someone to change the name. The page would look like this (I'm not making this pretty):

<% using (Html.BeginForm()) { %> <%: Html.LabelFor(model => model.FirstName) %> <%: Html.TextBoxFor(model => model.FirstName) %> <%: Html.LabelFor(model => model.LastName) %> <%: Html.TextBoxFor(model => model.LastName) %> <input type="submit" value="Submit" name="submitButton" /> <% } %>

This is the important part about getting data back and forth between Controllers and Views. What we are doing here is that we are taking your strongly-typed view (which is typed with the Person class) and using helper methods (like LabelFor and TextBoxFor) to tie the model together with its data and, ultimately, together with the actions contained in the controller (which we have to finish developing here in one moment).

So, you can now see the data. But, if a user changes the name and clicks submit - we want the page to display the new name. This means we need to add one more action to MainController - the one that receives the data.

[HttpPost] public ActionResult Index(Person person) { // Do whatever you want with the Person model. Update a database, or whatever. return View(person); }

This action looks very similar to the other action we just developed. However, this one takes a person object (from the form that is being submitted) and it gives the controller an opportunity to do whatever needs to be done with that object. Once this is done, you can choose to redirect to a different page, redisplay the page (useful if there are errors), or do any number of other things.

Again, this is ALL covered (and much more) in the NerdDinner Tutorial. I highly recommend you read and follow through that.

As for the AJAX-y aspects you discussed, the premise is still the same (although there is a little bit of JavaScript/jQuery work that goes on in there). I won't go into it now, but the basics are also covered in the NerdDinner tutorial.

I hope this gets you started. I remember being a bit confused too when I first started working with web technologies, so I hope this helps you out!

Edited by RameshRajendran on Nov 06, 2012 07:08 AM
Edited by RameshRajendran on Nov 06, 2012 07:08 AM
Marked as answer by Young Yang - MSFT on Nov 12, 2012 12:59 AM

Reply

Xequence

Contributor

4313 Points

1528 Posts

Re: MVC Passing value from view page to controller

Nov 06, 2012 02:38 PM|LINK

it boils down to httppost, httpget in your action methods. going over the tutorials from the beginning is the only way to understand what you are doing other than guessing

Mysite
Credentials

MVC Passing value from view page to controller RSS

10 replies

Mahesh108