Intelligently Handle/Cache Downloaded .js Assemblies
Keeping with the idea of supporting Silverlight5 as a baseline. :)
CSHTML5 is a great idea and fits nicely if it is to be packaged and installed via an App Store. However, in the context of a web-hosted application (from a web server), downloads might take a while, especially on a mobile device (and especially if you refresh the page after downloading).
This vote ensures that this is accounted for, and that CSHTML5 intelligently ensures that files are stored on the user's device so that when a load (or refresh) occurs, a minimal amount of downloading occurs.
For instance, let's say a client downloads CSHTML5 Application A, and it has a reference to Microsoft.Practices.Prism.Composition.js. The client downloads this .js file and places it in its cache.
Now let's say that this same client visits and downloads CSHTML5 Application B. Application B also has a reference to Microsoft.Practices.Prism.Composition.js. Instead of downloading this file again, CSHTML5 first searches its cache and uses the .js found there, instead.
100000 % agree with you !!