Shawn Wildermuth wrote about his experience using ASP.NET MVC for a new site he developed.
One of the things he does is sending "complex" models to the view to render, I'm not sure that's something you should do. I believe that you should stick so simple strings and have the controller do all the heavy lifting. It's a slippery slope you're stepping on, before you know, you're sending 'models' straight from the Entity Model to the view.
Not sure if that's really feasible (or the simplest/easiest) in all situations, but it ensure a clean separation between business logic in the controller and the model and the UI in the view.
More info:Enforcing Strict Model-View Separation in Template Engines (pdf)