title: WinDbg environmental variables
body: <p>When using WinDbg to debug an executable, is there a way to specify a batch script to run before debugging starts to set up environmental variables for the debug session? </p>
  
  <p>I'm attempting to mimic an automated test environment where this executable will run. The variables contain information like what the current build number is, where the results directory is and where the 3rd party tools directory is located. I could hard-code these into the application for my own testing, but that's ugly :). </p>
  
  <p>This is of course on a Windows OS, and I would rather not use a different debugger.</p>
  
  <p>If WinDbg doesn't support this directly, what is the best way to achieve this functionality?</p>