title: Evaluation Copy of InstallShield and Version Control
body: <p>My employer currently has access to a singular InstallShield 2016 Professional key. They're looking at upgrading to 2018 Premier and getting a second license, but want me to test out 2018 Premier by working with our actual installer. All of our installer files are checked into version control with the rest of our project.</p>
  
  <p>According to Flexera's documentation, an evaluation copy of InstallShield implements a time limit for running setups produced by it. Makes sense - they don't want you creating your installer in the 21 day limit and then never buying the product.</p>
  
  <p>If I'm careful not to implement anything specific to 2018 or Premier, will checking in anything I create and having it re-built on the machine with the full license avoid triggering this restriction? There are concerns that using the evaluation copy of 2018 Premier in an actual working environment will ruin what's already checked into version control and implement a five-day limit for our installer.</p>
  
  <p><strong>Note:</strong> We do plan on using the evaluation copy only as an evaluation. The trial period will be to determine how much more efficient it is to have two devs working on the installer, as well as to figure out if upgrading to Premier is worth the cost. We may or may not end up purchasing a second license at the end of the trial.</p>