I'm sorry, I do not quite understand what you mean by 'provided targets'. I
used the following command in the Post Build event for the bundle project:
(The certificate was previously imported into a local catalog. This is the
same command that I also use in the Post Build event for my MSI
I just read the doc for Insignia more carefully and I think I see what I am
doing wrong. I had originally not used insignia because it seemed to be
needed for signing 'external CABs' and I am not using an external CAB. But
I now see how it is use to extract the engine.exe from a bundle. I will
Mission accomplished! thanks for the assistance.
Phill
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Unspecified-Error-after-signing-bundle-tp7587845p7587864.html
Sent from the wix-users mailing list archive at Nabble.com.
I have a bundle which has three EXE and 1 MSI, all third-party, and then my
MSI for a total of five packages. This is my first bundle and it has been
installing on a Win 8 x64 test system successfully. I install and uninstall
on this test box, rather than going back to a clean OS as I have
Make sure you are signing your bundle using the provided targets. If unsure,
post what you are using.
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: Tuesday, August 06, 2013 4:29 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Burn 'Unspecified
Realize that signing a bundle requires two signatures in a row. Make sure you
are signing the right thing in each target.
From: jacob.hoo...@greenheck.com
To: wix-users@lists.sourceforge.net
Date: Tue, 6 Aug 2013 21:37:45 +
Subject: Re: [WiX-users] Burn 'Unspecified Error' after signing
6 matches
Mail list logo
