We're already using that technique. At the moment when you're starting C1 console, by pressing "Shift" in the login screen, you can choose between
a) "Normal" mode - the majority of js and css files are "compiled" to files "/Composite/scripts/compressed/*.js" and "/Composite/skins/skin_compiled.css"
b) "Debug" mode - all js and css files are loaded in a normal way so it is easy to debug js, and find right css file to fix
and DOM rendering. The best way to see this is to see how quick C1 console works on Chrome, we did it on an internal build it is much, much faster.
>> As a sidenote you should use .ashx handlers instead of .aspx for serving the scripts and css on the server. It takes less resources for the asp.net runtime to instantiate whatever class that implements IHttpHandler than creating
a full Page-object.
aspx -> ashx - good point!