ASP.NET MVC - Strongly typed view model, where does it belong?

I'm trying to create a strongly typed view model as John Sheehan suggests here. Where should it go? I can make arguments to myself for Model, View, a开发者_如何学Cnd Controller.

It should go in the "Models" directory of the web app. ViewModels are by definition specific to one or more views and therefore belong in the web app, not the core.

You could define them in the controller that uses them, but this doesn't scale. Same with defining the class in the view code. Even though one-class-per-file means more files, its easier to find code and easier to maintain.

I'll often create a subfolder for each controller, so I end up with things like Web.Models.Foo.BarViewModel.

If have them in my Domain project in a PresentationModel directory and like @Seth Pretry-Johnson, I have them in separate Controller directories.

This is my overall structure of a project:

• Website Project
  • Controllers
  • Views
  • Etc
• Domain Project
  • Models
  • Repositories
    • Abstract
  • Services
    • Abstract
  • PresentationModels
    • Home
    • User
    • Etc
• DataAccess Project
  • Repositories

HTHs (and doesn't raise more questions.. ;-),
Charles

I put the actual model class in the Models folder.

/Controllers
/Models
    /Entities
    /Mappings
    /ValueTypes
    /ViewModels

Something like that. I'm a big fan of the Fluent NHibernate.

It can go wherever you want it to go, why do you need someone to tell you where to put a class?

A lot of people have the wrong idea that, unless you put your classes inside some specific directory grouped by functionality, things will not work. This might be true with other frameworks, but with ASP.NET MVC it's not true. Code is compiled to assemblies.