Thanks very much, Jacob - it’s working! In case it helps anyone else: it works to use kSignCMD.exe (free download from K Software) in place of the 2 calls to signtool.
> On Jul 6, 2015, at 4:13 PM, Hoover, Jacob <jacob.hoo...@greenheck.com> wrote: > > The error you are getting is: FDIERROR_NOT_A_CABINET > > (This would go after your last call to light.) > > http://neilsleightholm.blogspot.com/2012/05/wix-burn-tipstricks.html > > Signing a package > > insignia -ib Setup.exe -o engine.exe > signtool engine.exe (extra parameters excluded for simplicity) > insignia -ab engine.exe Setup.exe -o Setup.exe > signtool Setup.exe > > Though it's easier to use a wixproj and the MSBuild tasks, and then just > override the targets. > > -----Original Message----- > From: David Burson [mailto:david_bur...@ntm.org] > Sent: Monday, July 06, 2015 1:01 PM > To: General discussion about the WiX toolset. > Subject: [WiX-users] how to add code signing to build script > > Hi, > > I’m brand new to code signing. Just got my certificate through K Software, a > Comodo reseller. I tried adding a call to kSignCMD.exe at the end of my > build script, and it appears to work: the properties for my installer show > my certificate, and the UAC prompt when I install also shows me as the > publisher. > > However, the installer fails. The start of the log looks fine as far as I > can see, but here’s how the log ends: > > Apply begin > Creating a system restore point. > Created a system restore point. > Caching bundle from: > 'C:\Users\david\AppData\Local\Temp\{e3cdbd3a-6ab1-4f6c-94b2-4f005172e581}\.be\MapCreatorSetup-x64-1.1.3.exe' > to: 'C:\ProgramData\Package > Cache\{e3cdbd3a-6ab1-4f6c-94b2-4f005172e581}\MapCreatorSetup-x64-1.1.3.exe' > Registering bundle dependency provider: > {e3cdbd3a-6ab1-4f6c-94b2-4f005172e581}, version: 1.1.3.0 Acquiring container: > WixAttachedContainer, copy from: C:\mc\MapCreatorSetup-x64-1.1.3.exe > Setting string variable 'WixBundleLastUsedSource' to value 'C:\mc\' > Error 0x80070001: Failed to extract all files from container, erf: 1:2:0 > Error 0x80070001: Failed to wait for operation complete. > Error 0x80070001: Failed to open container. > Error 0x80070001: Failed to open container: WixAttachedContainer. > Failed to extract payloads from container: WixAttachedContainer to working > path: > C:\Users\david\AppData\Local\Temp\{e3cdbd3a-6ab1-4f6c-94b2-4f005172e581}\F0BE7EF5275BEDA1781A0DC8690CC9EBB929A6A8, > error: 0x80070001. > Error 0x80070001: Failed while caching, aborting execution. > Removed bundle dependency provider: {e3cdbd3a-6ab1-4f6c-94b2-4f005172e581} > Removing cached bundle: {e3cdbd3a-6ab1-4f6c-94b2-4f005172e581}, from path: > C:\ProgramData\Package Cache\{e3cdbd3a-6ab1-4f6c-94b2-4f005172e581}\ > Apply complete, result: 0x80070001, restart: None, ba requested restart: No > > I’ve examined this Insignia documentation: > http://wixtoolset.org/documentation/manual/v3/overview/insignia.html but I > don’t really understand what I’m supposed to do to get code signing to be > part of my build script. Here are what I assume is the pertinent information > about my build script: > > After my build script builds all the components and produces an .exe, it > calls candle.exe on about a dozen .wxs files, representing various components > such as localization, help file, license, and finally the actual product. > > Next, it calls light.exe with the .wixobj’s produced in the previous steps, > to create an msi. > > Then it calls candle.exe on my bundle.wxs. > > Finally, it calls light.exe on the bundle.wixobj. > > Where in these steps should I insert call(s) to sign my code, and what should > those calls look like? Also, is there any command I can add to the script > that will output whether code signing worked? > > Thanks, > David > > ------------------------------------------------------------------------------ > Don't Limit Your Business. Reach for the Cloud. > GigeNET's Cloud Solutions provide you with the tools and support that you > need to offload your IT needs and focus on growing your business. > Configured For All Businesses. Start Your Cloud Today. > https://www.gigenetcloud.com/ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ > Don't Limit Your Business. Reach for the Cloud. > GigeNET's Cloud Solutions provide you with the tools and support that > you need to offload your IT needs and focus on growing your business. > Configured For All Businesses. Start Your Cloud Today. > https://www.gigenetcloud.com/ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
