At first glance I'd say to SuppressSignatureVerification=yes but that's
already done. What about keeping the SQL install locally without
downloading and therefore modify the ExePackage definition accordingly?
(Remove everything beginning with RemotePayload... Or what about re-sign
the SQL
Since you're using a RemotePayload element, the
SuppressSignatureVerification isn't going to do anything. You will want to
remove the certificate information from the RemotePayload and populate the
Hash instead.
On Wed, Jul 10, 2013 at 11:58 PM, Tobias S tobias.s1...@gmail.com wrote:
At first
for Windows Installer XML toolset.
Objet : Re: [WiX-users] Burn : SQL Express 2008 R2 certificate problem
Since you're using a RemotePayload element, the SuppressSignatureVerification
isn't going to do anything. You will want to remove the certificate information
from the RemotePayload and populate
Hello,
I'm trying to chain many prerequisites to my product : .NET 4.0 or 4.5, IIS and
SQL Server Express which has some prerequisites too : .NET 3.5, Windows
Installer 4.5, Powershell. It needs to work under Windows Server 2003 SP2, 2008
SP2/2008R2 RTM and 2012 RTM.
I'm near the goal, but I
4 matches
Mail list logo