ely load multiple scenes, so the level designer(s) have one scene without functionality to work on, and programmers (who don't need a lot of time with a scene) have a "bootstrap" scene, which contains game functionality.



Q:

Installing dev tools in production

What are the reasons for not installing VS 2008 on a live production web server?

A:

Given the comment the OP made giving a reason why you would do this:

Would make "works on my machine"
  issues easier to debug

Then my answer for why it should not be installed is: to remove the temptation to try and debug problems on the live production Web server.

A:

The biggest reason for not installing it:
It would mean you were not doing an incredibly silly thing on your production server.
If you cannot replicate issues in code on your development machines then you need to create a staging server that exactly replicates the configuration and environment of your production environment. If you still can't replicate the fault on that, it means you have either a: failed to replicate the environment well enough, b: do not understand your configuration on your production environment well enough to be able to replicate it or c: have not properly configured your application to deal with the change in environment.
Another reason:
You don't have to have a copy of your source-code on your server and the ability to easily compile it in place. If you ever get hacked, you'll be glad you didn't do that as your source code will get stolen and/or the hacker will have an extremely easy way to insert malicious code into your app.

A:

I concur with some of the posts that explicitly states that you should neither be doing development nor debugging on production. If an error should occur, ensure that you have a procedure in place to log the necessary data.
If any issues should occur while deploying new code, revert back to the old one and use the (exception)data to troubleshoot the code back in your development or your staging machine.
The production server should only have the bar