title: Installshield 64-bit project setup
body: <p>What is the best way to use InstallShield to generate installers for both 32 and 64-bit environments? The majority of my application is bit-neutral (.net, Java, data files).  I would prefer it if I only had to package up those files once.  Is there a standard approach to reducing the maintenance of the installshield projects? Currently the only solution I can find is to have two duplicate projects, where each of the components are flagged with 64-bit and the default install directory set to ProgramFiles64.  There must be a better way to do this!</p>
  
  <p>Only a very small portion of my application cares how may bits it is being executed on. We have a few C++ DLLs and JNI calls that need to be different.  Most of this is determined at runtime by checking if the JRE we are running on is 64-bits.</p>
  
  <p>I would like to avoid distributing two 130 MB files, and ideally ship one big zip file that has both installers in it, each referencing common components.  Do I need to create merge modules for the common things and reference them in each of the projects?</p>
  
  <p>We are using InstallShield 2009 (Premier) if that matters. </p>