Research & Development for 3D & the Web

A quick brain dump on compiling code for the web:

Recently at work there was discussion on the topic of compiled code vesus un-compiled code when building websites. What should be compiled and what shouldn’t be or can’t be.

I like the idea of compiling code when developing – it’s relatively new to me strangely having a mixed coding background and creative industries background but compiling all of your code behind files into a .dll file and keeping your front end files separate makes perfect sense since any quick changes which need to be made to a site are 9 times out of 10 going to be layout/design changes which can be looked after in the aspx files or whatever front end files are being used and the style sheets.

The benefits are that when deploying you only need to upload a re-built .dll and any aspx/ascx/css files that are requied as well as ensuring that your all important source files aren’t sitting up on your live server where any clown with access can get to them. Doing it in this way also means that the simple layout and design stuff which you can usually access if you really wanted to through markup of a page can still be altered quickly as they inevitably need to be when a client asks.