Continuing the topic of smartening up Visual SourceSafe - how might we compensate for its inability to lock a branch?

One way would be to notify those concerned when a revision a.k.a. check-in occurs. Certainly one approach would be to create a CruiseControl.NET project that merely notifies when check-ins occur.

For a low-tech solution I use this approach. No attempt was made on usability - so improvements should come easy.

• edit yasm.exe.config to specify your sendmail server
• edit revision-watcher.cmd to specify your script settings