title: MSBuild: error MSB3147: Could not find required file 'setup.bin'
body: <p>I'm trying to use MSBuild (under CruiseControl) to build the installation for my .NET 4 app. The installation build should create a boostrapper to install the prerequisite (.NET 4 and Windows Installer 4.5 in this case), this is done using the <a href="http://msdn.microsoft.com/library/ms164294.aspx">GenerateBootstrapper Task</a>.</p>
  
  <p>Running <code>MSBuild.exe project.msbuild.xml</code> from the command line on a development machine, which has VS 2010 installed, works fine. Running on the build machine, which only has the latest Windows 7 SDK, fails with the error:</p>
  
  <pre><code>(ProductDistributions target) -&gt; bootstrapper.xml(236,5): error MSB3147: 
  Could not find required file 'setup.bin' in '&lt;project path&gt;\ProductDistributions\Engine'.
  </code></pre>
  
  <p>On the dev machines, I have a <code>C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Engine</code> folder containing a <code>setup.bin</code> file, but on the build machine there is no <code>Bootstrapper</code> folder inside <code>C:\Program Files\Microsoft SDKs\Windows\v7.1</code> (the 7.1 vs 7.0A is apparently because VS2010 installs 7.0A, but the standalone SDK is 7.1).</p>
  
  <p>Also, on the build machine there is no 4.0 registry key inside <code>HKLM\Software\Microsoft\GenericBootstrapper\</code>, but the dev machines do have one containing a path string with a value of <code>c:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\</code></p>
  
  <p>It looks like there's something I need to install on the build machine to add the Bootstrapper folder to "Microsoft SDKs\Windows\v7.1"  (and setup the registry keys), but I'm not sure what that is. Any idea what I need to get?</p>
  
  <p>Or is there something else I need to get my installation build working?</p>
  
  <p><strong>Updated:</strong> I have this working at the moment by manually copying the 7.0A bootstrapper folder from a dev machine onto the build machine, and manually adding that path to the <code>HKLM\Software\Microsoft\GenericBootstrapper\4.0</code> registry key. Which seems to work, but it seems like this can't be what I'm supposed to do to fix the problem. So I'd appreciate if anyone has a less-hacky solution to this.</p>