1) immediate custom action since it does not change machine state (and you want
to set properties);
2) have an input property containing either the possible domain account or a
reference to a property containing the possible domain account;
3) use C# in the usual manner -- you can adapt code
Brian the Wix documentation defines both a HeatDirectory Target and a
HeatDirectory Task.
I provided incorrect information in this thread and I appreciate John's
prompt to go research this in more detail. There is a HarvestDirectory
target and a HeatDirectory task. Here is an example of
When you open your 64 bit package with Orca and look at the Summary
Information does it indicate that it is a 64 bit package?
--
View this message in context:
We have created a WIX installation MSI that installs certificates to machine
store. It installs a root certificate (GoDaddy Class 2 Certification
Authority) to the Trusted Root Certification Authorities. It works for most
of machines, but it fails some machines. We suspected the group policy
Yes, Orca Summary shows it with Platform x64.
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: Friday, November 14, 2014 6:33 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a
64-bit MsiPackage
Custom actions are hosted by Windows Installer in a separate custom action host
process based on custom action type.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Ryan
OK, so, is there a way I can achieve what I need to achieve? Run this CA in a
64-bit process?
-Original Message-
From: Rob Mensching [mailto:r...@firegiant.com]
Sent: Friday, November 14, 2014 7:53 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] [SPAM] Re:
This might be a regression, though I haven't dug to history to see if it was
intentionally changed back.
Ref:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Certificate-install-to-local-machine-fails-with-code-26352-td1121050.html
From the current certutil.cpp
if
What is the bitness of your CA DLL? Just a stab in the dark but you might need
to have it compiled twice, once as 32 and once as 64, and have the respective
MSI package use the right CA DLL.
-Original Message-
From: Rob Mensching [mailto:r...@firegiant.com]
Sent: Friday, November 14,
That is the technique I use and it is necessary when access 64-bit-only file
system locations and the like.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
Thanks.
I will check to see if the user has the root certificate already.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WIX-Installation-fails-to-Install-Certificate-to-Root-Certification-Authorities-for-Some-machines-tp7597941p7597948.html
Hi,
How do I use a property set to RadioButton in a Feature condition?
I have a Secure property called UNICODETYPE which gets set to the value of
radio button selection.
I want to use that property to decide which feature to install.
Do the Level of parent feature matter, note it is 200. My
To expand on what Rob said, it all just works. On an x64 system the
MSI service will be 64-bit. If you have a 32-bit CA you'll get a
32-bit msiexec process launched to host it. If you have another CA
that requires impersonation, you'll see another msiexec process
running impersonated. The error
So something is checking the platform setting on the dll ?, With VS2012 and
VS2013, I'm getting problems if I start to set platform to anything else
than anycpu on dll's now, what gives?
On Fri, Nov 14, 2014 at 6:38 PM, Phil Wilson phildgwil...@gmail.com wrote:
To expand on what Rob said, it
Yes something is checking the platform setting. Your comment is
otherwise too vague. Since you need separate setups for 32-bit and
64-bit systems it's often best to make sure that all the code that
runs during the install is of the appropriate bitness. You don't want
a 32-bit (64-bit) hosting
Just to add something that may be the issue with your setup. The call
stack is driven by the architecture of the starting process or Dll, so
if you have a 32-bit CA Dll then msiexec will be a 32-bit process to
call it. Your Dll then calls other Dlls. and If all these other Dlls
are AnyCpu then
and by will be built with the caller's architecture I mean JIT
compiled to the caller's architecture because this is happening at
run time.
---
Phil Wilson
On Fri, Nov 14, 2014 at 10:29 AM, Phil Wilson phildgwil...@gmail.com wrote:
Just to add something that may be the issue
In my case, my CA dll is built as AnyCPU. So it seems I need to build it
separately for x86 and x64. I will try that. Thanks!
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: Friday, November 14, 2014 10:38 AM
To: General discussion about the WiX toolset.
Hi,
I am trying to install .NET 4.5.1 as a prerequisite
to our Wix bootstrapper, and we don't see any
messages about the packages installed (e.x KB,
VC runtime etc). It just shows Installing dot net
4.5.1 . Can someone help me outline the steps
required to get the status messages in Bootstrapper
19 matches
Mail list logo
