What does the output of MSBuild look like when you build your bundle?  Is 
signtool being called? (If you can't see it in the logs, you may have to 
increase the verbosity.)

For the MSI/CABS,

  <Target Name="SignCabs" DependsOnTargets="UsesSignTool">
    <Exec Command="&quot;$(SignToolPath)&quot; sign /t 
http://timestamp.digicert.com /a &quot;%(SignCabs.FullPath)&quot;" />
  </Target>
  
  <Target Name="SignMsi" DependsOnTargets="UsesSignTool">
    <Exec Command="&quot;$(SignToolPath)&quot; sign /d &quot;App  Setup&quot; 
/t http://timestamp.digicert.com /a &quot;%(SignMsi.FullPath)&quot;" />
  </Target>

For the bundle,

  <Target Name="SignBundleEngine" DependsOnTargets="UsesSignTool">
    <Exec Command="&quot;$(SignToolPath)&quot; sign /d &quot;App Setup&quot; /t 
http://timestamp.digicert.com /a &quot;@(SignBundleEngine)&quot;" />
  </Target>

  <Target Name="SignBundle" DependsOnTargets="UsesSignTool">
    <Exec Command="&quot;$(SignToolPath)&quot; sign /d &quot;App Setup&quot; /t 
http://timestamp.digicert.com /a &quot;@(SignBundle)&quot;" />
  </Target>

-----Original Message-----
From: Brian Enderle [mailto:bria...@gmail.com] 
Sent: Thursday, December 12, 2013 3:49 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Using signtool to sign bootstrapper

I have the following in my wixproj file:

  <Target Name="SignBundleEngine">
    <Exec Command="&quot;C:\Program Files (x86)\Microsoft 
SDKs\Windows\v7.1A\Bin\signtool.exe&quot; sign /f 
&quot;$(ProjectDir)*****.pfx&quot; /p ***** /d &quot;Utilities&quot; /tr
http://timestamp.comodoca.com/rfc3161 /v &quot;@(SignBundleEngine)&quot;" />
  </Target>
  <Target Name="SignBundle">
    <Exec Command="&quot;C:\Program Files (x86)\Microsoft 
SDKs\Windows\v7.1A\Bin\signtool.exe&quot; sign /f 
&quot;$(ProjectDir)*****.pfx&quot; /p ***** /d &quot;Utilites&quot; /tr
http://timestamp.comodoca.com/rfc3161 /v &quot;@(SignBundle)&quot;" />
  </Target>

Yesterday this was working correctly to sign my Setup.exe file but today it 
does not work to sign the file.  I cannot think of anything that changed since 
then but today the Setup.exe file is not getting signed.

I am also using the following Post Build command to sign an MSI file that is 
part of Setup.exe and it works correctly.

"C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Bin\signtool.exe"
 sign  /f "$(ProjectDir)*****.pfx" /p ***** /d "Utilities" /tr
http://timestamp.comodoca.com/rfc3161 /v "Setup.msi"

I do have to set the "Run post-build event" to "Always" as there are some ICE 
errors I have been unable to resolve but don't seem to affect the program.  Is 
there a way to tell the wixproj to also "Always" do the signing regardless of 
the outcome?


Brian Enderle

If you can't explain it simply, you don't understand it well enough.  - Albert 
Einstein
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance affects 
their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & 
PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to