gning,
and then once for the .cer file I included in the msi.
From: Rafael Rivera [raf...@withinwindows.com]
Sent: Thursday, July 02, 2009 4:03 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching a product witho
e msi.
From: Rafael Rivera [raf...@withinwindows.com]
Sent: Thursday, July 02, 2009 4:03 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching a product without elevation
MSI (c) (24:FC) [15:23:03:419]: Certificate of s
ge that I noticed in the patch log:
>
> [snipped]
>
>
> -Original Message-
> From: Rafael Rivera [mailto:raf...@withinwindows.com]
> Sent: Thursday, July 02, 2009 3:17 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Patching a p
I did run signtool against the packages, with the command lines in the first
part of the post.
I also forgot to point out a couple of other changes to the demo code. I
changed the installer version to 300, and I set ALLUSERS to 1 to make sure that
I installed per-machine to start with.
Someth
Chris,
Those elements appear to simply identify what certificate should be
given the green light for patching. I believe you still need to
digitally sign the resulting MSI using signtool.exe.
- Rafael
Chris Bardon wrote:
> My goal for getting patching to work is to be able to deploy an applica
My goal for getting patching to work is to be able to deploy an application
that can be patched by a non-admin user, but I'm running into a problem. I've
created the patching sample in the documentation, and the patch works when it's
elevated, but whether or not it's signed, the patch is still
6 matches
Mail list logo
