I've become aware of an itch due to some non-DRY code pertaining to view model classes in an (ASP.NET) MVC web application and I'm thinking of scratching my itch by organizing code in various 'partial ...
How do you organize an ASP.NET MVC 3 application with potentially hundreds of views but with only a few entry points?
Assumptions: Minimalist ASP.NET MVC 3 application for sending emails where the view represents the contents of an email. Over 500+ email types. I would NOT like to have 500+ actions in my controller ...