title: Visual Studio (C#) Build Output path using environmental variables
body: <p>Is it possible to use environmental variables in the build output path in VS 2008 (et al)/ I'm trying to find a solution where several developers on my team using both Windows XP &amp; 7 and all with different Windows logons, can all modify projects <em>and</em> common referenced dll's (source held on Source Safe) and not screw up the relative paths? I've tried such things as %userprofile% and $(userprofile).</p>
  
  <p>I've looked into post build events but these do not really seem to provide an anawer to my problem. Sadly I'm not in the position to use 3rd party add-ons either as these will be non-commercial and it's nearly impossible to get authorization for any licences for them.</p>
  
  <p>(Similar unanswered question at <a href="https://stackoverflow.com/questions/3967431/output-path-for-build-in-visual-studio-2010">Output path for build in visual studio 2010</a>)</p>