title: Visual Studio: Automatic COM registration with dependant DLLs outside Debug/Release dirs
body: <p>I've written some unmanaged C++ COM DLLs that rely on native C++ DLLs not in the system path.  When I build the associated projects without copying the DLLs into the Debug/Release directories I get the infamous PRJ0050 compiler error.  </p>
  
  <p>Clearly I could copy required DLLs all around the solution, but I'd like to avoid this.  I know I could set project properties Linker->"Register Output" to No and then run regsvr32 directly during a post build step.</p>
  
  <p>My question is if there's a better way to do this.  Is there a way to use the automatic "Register Output" option with a custom path controlled at the project level?  What am I missing here?</p>
  
  <p><strong>Edit:</strong> Originally I'd been thinking "Register Output" did some magic like un-registering on a clean, but that isn't the case.  The only thing special it seems to do is pick out the proper way to register different types of projects.  </p>