Moving to wix-devs.
The WiX toolset is
delay signed in the build. That code won't run unless you do one of the
following:
1. Use sn.exe to
trust the delay signed binaries (sn.exe -Vr I think is the right switch)
2. Resign the
binaries.
Doing #2 will give you
a completely different set of binaries for the WiX toolset (the public key
token will be different) I explicitly do not redistribute the privatekey
for the WiX toolset so that we can tell when people have their own private drop
of the toolset.
Also, can you provide
a little more detail why you're doing this? Is this a bug in the WiX
toolset that needs to be fixed?
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Shmarya Rubenstein
Sent: Thursday, May 11, 2006 10:22
AM
To:
[EMAIL PROTECTED]
Subject: [WiX-users] Compiling Wix
Hi all,
I'm experiencing something pretty wierd when compiling WiX.
I made a number of small changes to the WiX DifX extension and teh NAntTasks,
and decided to compile everything under .NET 2.0
Everything was going great until I tried to copy the binaries to another
machine.
I now get the following error when trying to run any of the WiX exes:
Unhandled Exception: System.IO.FileLoadException: Could not load file or
assembly 'candle, Version=3.0.1703.0, Culture=neutral,
PublicKeyToken=36e4ce08b8ecfb17' or one of its dependencies. Strong name
validation failed. (Exception from HRESULT: 0x8013141A)
File name: 'candle, Version=3.0.1703.0, Culture=neutral,
PublicKeyToken=36e4ce08b8ecfb17' ---> System.Security.SecurityException:
Strong name validation failed. (Exception from HRESULT: 0x8013141A)
The Zone of the assembly that failed was:
MyComputer
I need my patch working urgently...
What am I missing?
Thanks,
--
Shmarya
-----------------------------------------------------------
[EMAIL PROTECTED]
- http://idp.shmarya.net
