I think you’re saying that you can pass (for example) an instance of the Person “model” to the controller. While that does provide type safety, it’s a fairly trivial case. Passing a concrete type means that separate concrete datatypes would needed for nearly every view and, in any reasonably sized web app, that means hundreds of datatypes. This is my basic gripe (not with ASP.NET, but with statically types languages in general). I would love to find a way to stuff a bunch of variables into a heterogeneous collection and be able to prove that the controller and view were in-sync. Unfortunately, this looks like a seriously non-trivial problem since Views may or may not access certain parts of datatypes/structures making it difficult to understand whether an inbound datatype will satisfy completely the view.