I have just started looking at ASP.NET MVC once again  One of the first things that I noticed when trying to create a real project using ASP.Net MVC is that the very clear seperation of concearns that helps to make testing easier also makes it difficult to compose feature rich pages made where a user can perform more than one self contained action. This actually really apeals to me as this would give you very minamilistic and focused screens in your applcation.

However, this isn't typically the way that when working with clients that they ask for there screens to be designed. Clients often want screens that break this model. The reason behind this is that from a useability point of view this will often make it much faster and easier for the end user to do there work. With this in mind I know that to use MVC in a way that suits both me and my clients I must find a way of using MVC that will be easilly testable and will allow composition of component type elements in a view. 

 I have spent quite a while looking at this on the Internet and it seems there are various solutions to this problem. I found what I beleive to be both the most lightweight and best solution for my purposes along with a good discussion on the availiable option on Steve Sanderson's blog. I would encorage anyone facing this perticular dilema to take a loot at the discussion over on Steves site.