>The problem with all of this is that it's not super stable. if files are open things can be locked etc. which is a bitch. Using project hooks are a good way around this but I don't use projects much except for final builds so that doesn't really work for me.
>
>Ultimately you want to have a Build routine that can put your project into a stable commit state. This can be a PRG that clears and closes everything then creates the text files.

I sometimes work in a setup where dev is responsible for checkin, and from there a dedicated build VM does a checkout of changed files into the VM project directory and attempts to build there in continuos integration manner, showing success/failure for each part in a simple red/green GUI if any failures crop up.
Clearly Build process is unhampered and in case of failure offending part is easy to find in most of the cases. Took some tweaking to set up even after german devcon session, but was/is worth it even for 2-4 devs working in parallell.