title: Why does regasm /regfile seem incomplete?
body: <p>I have a .NET assembly I need to register at install time.  I'm noticing that the registry has subtle differences when <code>regasm</code> is used directly versus being installed via <code>regasm</code>'s registry script.</p>
  
  <p>Here's my test:</p>
  
  <p>I export the original HKCR hive, then run: <code>regasm my.dll</code></p>
  
  <p>From there, I export the subsequent HKCR hive and performance a diff.</p>
  
  <p>I then compare that diff with the output of <code>regasm my.dll /regfile</code></p>
  
  <p>There are a couple very important entries that get added via <code>regasm my.dll</code> that will never get added with the registry file output from the <code>regasm</code> command.  <strong>Why?</strong></p>
  
  <p>From an install point-of-view, I'd very much hate to call <code>regasm</code> during the install process.  I'd rather just run this .reg script.  I'm using InstallShield now, which under the hood is also missing the extra registry entries (it seems like it embeds the registry changes outputted with the <code>/regfile</code> flag).</p>