>>This is usually not an issue because anybody using the progam is running from an exe, and the clas libraries are compiled into it.
>
>Right, also, a development system and a production system should be used. Everyone should be running and testing from production, but the developer develops and tests in development.

Yeah. Ideally.

I'm learning as I go and haven't jumped into the turn-it-into-an-exe file learning curve yet. (Yes, my users are trusted and running a prototype that's in development mode). I'm sure compiling to an .exe is a breeze, once you know how to do it. But I don't have the luxury right now. Besides, when you work in a multi-developer environment, don't you still have the problem (he said naively)?

I mean, when you run in multi-developer development, don't you pull most of your source from the 'released' directory and overlay the parts you're working on with your new stuff? Not sure how that would work if the 'released' stuff is all .exe.fied.