How should I auto-fill the Html.EditorFor with a value in ASP.Net MVC3?

Question

I'm just taking a look at ASP.Net MVC3 and in one of the auto-generated views for Create, it uses "Html.EditorFor(model => model.User)" to provide a text box for the user to enter their username. Ideally, I would auto-populate this with @User.Identity.Name.

What is the correct way to achieve this? Does Html.EditorFor allow me to automatically populate it in the view, or should I be setting that at the controller when passing it in?

I've found that if I change the Create method in the controller from this:

    public ActionResult Create()
    {
        return View();
    }

To this:

    public ActionResult Create()
    {
        MyObject myobject = new MyObject();
        myobject.User = User.Identity.Name;
        return View(myobject);
    }

This seems to work. Is this the correct way to do this?

Thanks in advance for any confirmation that I'm doing this right.

Daniel A. White · Accepted Answer · 2011-05-04 13:29:03Z

4

Absolutely, the assignment is fine.

edited May 4, 2011 at 13:29

answered May 4, 2011 at 13:18

Daniel A. White

192k49 gold badges389 silver badges473 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Darin Dimitrov Over a year ago

There are no static classes involved.

Darin Dimitrov Over a year ago

no it isn't. It's a property on the controller which is an IPrincipal which has only a getter. This getter calls the HttpContext.User property which can be mocked. It is not static.

Darren Over a year ago

@darin-dimitrov Not sure what you meant about static classes being involved? Thanks for the responses though.

Darin Dimitrov · Accepted Answer · 2011-05-04 13:18:36Z

2

This is absolutely the correct way. You define a view model (MyObject) containing the User string property, then have your controller action instantiate and populate this model and finally pass the view model to the view for displaying. It is also easy to unit test because the User.Identity property on the controller is an abstraction that could be mocked.

answered May 4, 2011 at 13:18

Darin Dimitrov

1.0m276 gold badges3.3k silver badges3k bronze badges

Comments

Evgeniy Labunskiy · Accepted Answer · 2011-05-04 13:27:45Z

1

its a good way in this case, but if you bild a big project it's better to create a global model class where you will put all your models, not in controller.

answered May 4, 2011 at 13:27

Evgeniy Labunskiy

2,0424 gold badges27 silver badges45 bronze badges

1 Comment

Darren Over a year ago

Thanks. Which bit would go into the global model class -- the User.Identity.Name?

Collectives™ on Stack Overflow

How should I auto-fill the Html.EditorFor with a value in ASP.Net MVC3?

3 Answers 3

3 Comments

Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

3 Comments

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related