On 3/11/2011 9:27 AM, Kevin Burton wrote:
Along these same lines I tried building the CA project setting the target as
x64 just to see if this made a difference. I did get a different error
message but it still didn't work:
MSI (s) (60:80) [08:07:23:231]: Created Custom Action Server with
The bootstrapper redistributable components don't appear to ship with
the v7.1 Windows SDK. This could be a result of MS deprecating Visual
Studio's setup packages in favor of using InstallShield (blech) which
has it's own repository of redistributables. Or it may simply be that
those components
I'm building a chained installer (via the EmbeddedChainer element) that
chains a series of signed MSI packages together. As recommended by the
MSI documentation, I've added the signing certificate to my parent MSI,
like so:
PackageCertificates
DigitalCertificate Id=mycert
On Thu, 2010-11-11 at 15:30 -0800, Blair wrote:
I haven't tested this, but IIRC 32-bit processes get the 32-bit
environment variables, and the fact that candle is marked as a 32-bit
program should make the following work on both platforms:
?define DevExpressBin=$(env.ProgramFiles)\Developer
Hi,
Is there a way to tell, while building an installer package, whether the
building system is a 32-bit or 64-bit version of Windows?
We are starting to move some of the machines in our build farm and
developer's workstations to 64-bit Windows systems, but they are failing
on the WiX builds
5 matches
Mail list logo
