Home/ Questions/Q 975045
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T03:31:18+00:00

I’m familiar with the various bits of functionality of the MVC plugin to create

  • 0

I’m familiar with the various bits of functionality of the MVC plugin to create things. For example you can create a controller, write an Action method on it, then use the “create view” function in the context menu to create a view for it.

The question is, which is it recommended to do first?

I’m thinking I might start myself a methodology like this:

  1. Plan out what the UI etc will look like and how it will work.
  2. Write unit tests for the controller actions I think I might need.
  3. Create Controller (maybe with default CRUD actions if it’s to be that kind of controller).
  4. Create ViewModel class for each controller action.
  5. Create a strongly-typed view for each ViewModel.
  6. Start building the view, working back through the ViewModel to the Controller as the View is built up.

What do you think of this approach, and what do you do?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Sounds like you’re on the right track. Controllers are the most easily tested component of the three. Going controller-first will make it easier to follow Test-Driven Development practices.

    I’ve not been perfectly happy with the default view templates, but every MVC guru will point you to T4 templates, which let you roll your own. They, like the out-of-the-box view templates, will be more effective with existing view models and controllers.

    • 0