On the other 'sub-thread' I was suggesting using Angular + WebApi. Angular can handle all the routing for Views on the client side (rather than using a MVC controller) and pull data from a WebApi controller on the server. No round-trip to the server to create a View populated with data.

>Yup, which is why I was asking questions about it.
>
>>We've got crossed wires somewhere. This sub-thread has nothing to do with WebApi - just about looking at a MVC View using Page Inspector.....