KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
From this question , it looks like it makes sense to have a controller create a ViewModel that more accurately reflects the model that the view is trying to display. However, I'm curious about some of the conventions. Basically, I had the following questions: I, normally, like to have one class/file. Does this (preference) make sense with a ViewModel if it is only being created to hand off data, from a controller to a view? If a ViewModel does belong in its own file, and you're using a directory/project structure to keep things separate, where does the ViewModel file belong? In the Controllers directory? That's, basically, it for now. I might have a few more questions coming up, but this has been bothering me for the last hour, or so; and I can't seem to find consistent guidance, elsewhere. EDIT: Looking at the sample NerdDinner app on CodePlex, it looks like the ViewModels are part of the Controllers , but it still makes me uncomfortable that they aren't in their own files.
Tags (comma-separated)
Save Edits
Cancel