[wix-devs] Wix Burn and Windows App Certification Tests

[Michael birtwistle]

Yes it needs a formal InstallLocation concept. 
In my v3 fork I got burn to pick up the install location from the bundled msi, assigned it to a session variable and used that.  It's nice as you see it setting the variable in the setup log file after it install the msi. 

I'm also putting in a book flag so that the bundle UninstallString specifies /silent to make the unattended uninstall test work.

You were right about the programdata warning being simplistic. It's obviously ok to put package caches in the package cache folder after all :)

Thanks for your guidance. 
Mike Birtwistle


> On 5 Apr 2016, at 21:51, Rob Mensching <rob at firegiant.com> wrote:
> 
> Based on you last comment on the Github issue it sounds like this now behaves correctly and the outstanding work is to actually implement the InstallLocation concept for Bundles. Correct?
> 
> _______________________________________________________________
> FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/
> 
> 
> -----Original Message-----
> From: wix-devs [mailto:wix-devs-bounces at lists.wixtoolset.org] On Behalf Of Michael birtwistle
> Sent: Monday, April 4, 2016 3:47 PM
> To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
> Subject: Re: [wix-devs] Wix Burn and Windows App Certification Tests
> 
> Hi Bob
> Previously the warning for the 'install files to the correct folders' test was 'no install location was set for product {burn package name}'.
> Now that my proposed code change to burn has set an InstallLocation, wack has noticed that we (burn) has put a new executable under ProgramData, so it throws a tantrum about that instead.
> 
> installing the cached setup.exe to programdata feels to me like a violation. Setup.exe is not a data file. It's a powerful binary, that modifies the system.
> 
> Maybe you are right, that wack -might- not notice if I can somehow tell the bundle to use the install location as set by one of the payloads. However wack does take system snapshots before, during and after installation, so it could start to complain in future about that new .exe appearing under programdata after the install completes.
> At 499 pounds per certification submission, I really don't want to fail on a simple technicality like that.
> 
> Anyway, tomorrow I'll try hard coding an install location under program files, to test if wack, as it stands today, notices the new exe under ProgramData when I do that.
> 
> Thanks for all your help so far. 
> 
> Mike Birtwistle
> ____________________________________________________________________
> WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/