[wix-users] after build WixUtilExtension - "Strong name validation failed" on other machines

Bob Arnson bob at firegiant.com
Tue Aug 29 06:49:17 PDT 2017

Local builds of WiX aren't strong-name signed. The build turns off strong-name validation for the WiX public key token.

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Zoli P
Sent: Monday, 28 August, 2017 04:09
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: [wix-users] after build WixUtilExtension - "Strong name validation failed" on other machines


I had to fix a bug in the WixUtilExtension.dll source to support registry paths in quotes (I explained earlier on this mailing list under "heat generates different wxs after compiler change of our com dll" what was that exactly, change is in "\src\ext\UtilExtension\wixext\UtilFinalizeHarvesterMutator.cs").
Then I compiled with VS2015 cmd prompt + "msbuild wix.proj"
It works fine, I can use WIX on my machine.

However, when I copy the new binaries to other machines, and try to use WIX there, I have this error:

candle.exe : error CNDL0144 : The extension 'R:\External\Wix\WixUtilExtension.dll' could not be loaded because of the following reason: Could not load file or assembly 'WixUtilExtension, Version=, Culture=neutral,

PublicKeyToken=ce35f76fcda82bad' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)

I guess the msbuild did something on my machine what makes it work, and that is missing on the other machines? But with the original downloaded binaries, no such issue.
Why I have this error?
Do you know what is the best + quickest way to fix it? I could maybe try to switch off strong name validation for this file with "sn"...but maybe a better solution?

Thanks, Zoli

WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

More information about the wix-users mailing list