ASP.NET MVC terminology is tripping me up - why 'ViewModel'?
I'm an ASP.NET MVC newbie, but have used many Model-View-Controller frameworks previously. I recently came across the convention of gathering up the pieces of data that your particular view needs (indeed, it's assigned to the ViewData ) into a new class called (NameOfView) ViewModel . Gathering up this data so that it's associated with the functions provided by the View/Controller interaction strikes me as a helper struct, or even closure mechanism (in the 'encapsulates a collection of variables' sense). So why is it called 'ViewModel', given that it's neither a View or Model? Does anyone else