[wix-users] Program loses signature when bundled

[Hoover, Jacob]

Shouldn't have to compress.  I build my MSI's with external CAB's and I don't have any issues.  Are you using smart cab caching? 
Ex: 
<LinkerAdditionalOptions>-reusecab -cc "$(SomeMsbuildProperty\Cache\$(AnotherPropertyname)\"</LinkerAdditionalOptions>

Also, ensure you've done a clean before building the MSI, as you may be using 'stale' artifacts from a previous build.

Does your build process for your application sign the output before you invoke the build for the MSI?

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Patterson, Brent
Sent: Tuesday, August 30, 2016 4:00 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] Program loses signature when bundled

Apparently I need to compress the MSI files (change the MSI's Product.wxs from "compressed='no'" to 'yes"), then it's fine.  Guess I'll use that MSI approach then.  Thanks, your comment helped me start on the right path for investigating this!

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Hoover, Jacob
Sent: Tuesday, August 30, 2016 1:57 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] Program loses signature when bundled

Ensure your source location for your MSI is the signed exe.  Bundling a MSI will not modify a MSI package, nor any of its CABS. If you are using external CAB's, you can verify the contents easily by opening the CAB file and extracting the exe.  If it's an embedded CAB, then you will need a tool like Orca to extract the embedded contents.

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Patterson, Brent
Sent: Tuesday, August 30, 2016 12:57 PM
To: wix-users at lists.wixtoolset.org
Subject: [wix-users] Program loses signature when bundled

Thanks again for your help in the past, I really appreciate it.  I figured out the issue with patching bundle and MSPs.  The reason why it wasn't working correctly in past was due to me taking a shortcut in making MSPs.  Instead of updating files' version, I simply built them once, then twiddled with the MSI bundle to remove files as part of patching process.  This resulted in MSP thinking it's already installed, since all files are still at the same version, skipping some MSPs in the bundle.  But once I did a full rebuild for each patch, the MSPs worked correctly, both small and minor updates.

Now I'm facing an interesting problem.  I have a signing process that signs our program's exe (not the installer exe, but the program itself).  When MSI is built, it is still signed.  But once it's bundled as part of the bootstrapper bundle, it loses the signature and reverts back to unsigned exe.  Why is this?  Do I need to extract files (this is compressed into the exe) and sign it again and put it back in?  What am I missing here?

________________________________

Xactware's opt-in mailing list allows you to receive Xactware News that is of interest to you. Visit my.xactware.com today to join or to update your email preferences!

________________________________

This email is intended solely for the recipient. It may contain privileged, proprietary or confidential information or material. If you are not the intended recipient, please delete this email and any attachments and notify the sender of the error.

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/


____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/