title: Merits/demerits of using duck typed view models with ASP.NET MVC?
body: <p>What are the benefits/demerits of using duck typed view models with asp.net mvc? </p>
  
  <p>Recently <a href="http://amazedsaint.blogspot.com/2010/02/10-minute-twitter-search-app-using-duck.html" rel="nofollow noreferrer">I've seen an interesting implementation</a> of a twitter search client, using fluent C# dynamic XML wrapper to pass data from the controller to the view, to wrap XML data. </p>
  
  <p>It seems like a better way to pass data - viewModel.Foo instead of using ViewData["Foo"] or Foo.Bar instead of XElement("Foo").Attribute("Bar").Value in terms of cleaner code - but I assume it will be having performance issues.</p>