+4  A: 
public ActionResult GetOne(Int32 id)
{
      return View(id, "GetOne");
}

Specifying the view name explicitly overrides the default, which is to use the action key in the route values collection, which is equal to "GetAll" in this case.

Craig Stuntz
@Craig, Thanks for the answer! Do you consider it a normal practice to call actions within other actions? In my opinion one action should be independent from another action. This way they can easily be tested and used.
azamsharp
It is important to avoid duplication of code at all costs. There are many ways to do this, though. You could have two "independent" actions which call a shared function go get a model, e.g. In this case it seems clear that the same view should be used. So the view must be either specified explicitly or a shared view of some type (like MVC 2 default templated views) could be used. In other words, it depends on what you're doing.
Craig Stuntz
+1  A: 

ASP.NET MVC, like many MVC frameworks, makes a lot of assumptions based on convention. If you don't follow their convention, you'll have a little more work to do. In this case, the convention is that their is a view with the same name as your action, in the folder that corresponds to the name of your controller.

If you controller is UsersController, and your action is GetAll, it expects to find a view Views/Users/GetAll.

If you want to return a view that corresponds with a different action, you need to specify that (instead of using the default):

return View(id, "GetOne")
Matt
But I am calling the Action GetOne (whose view exists)?? The only difference is that I call it from another action.
Alex