You could have two .reg files one for each situation condition the customaction
using the Msix64 property.
Having said that, would recommend you use the Wix RegistryKey/RegistryValue
instead.
Michael
-Original Message-
From: Arun Kumar [mailto:arun_jku...@persistent.co.in]
Sent: Tuesd
Hi All,
I am writing 32 bit MSI and it has Custom Action to make some registry entries
using .reg file.
It works very well on 32 bit machine but on win7 64 bit machine the registry
entries are not redirected to HKEY_LOCAL_MACHINE\Software\WOW6432Node
My Custom Action looks like:
{
...
NOT Ins
Brilliant! Thank you very much, that's exactly what I was looking for!
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail
> -Original Message-
> F
On my machine the SQL CE registry keys have a value called
'DesktopRuntimeServicePackLevel'.
Have a look under:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server
Compact Edition\v3.5\ENU
or
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server Compact
Edition\v3.5\ENU
So
Anybody know of a good launch condition to determine whether "Microsoft SQL
Server Compact 3.5 Service Pack 2" (both 32-bit and 64-bit) are installed? I
want to disallow installation of my package if they are not installed.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
F
HI
One of two options. My recommendation would be don't use SQL Authentication
unless you really need to, or only provide it as an advanced option for SQL
upgrades. The SQL tool will use Integrated Auth if the SQL user and password
are left blank. That would mean that the user running the upg
Hello...
I created an installation 1.0 which creates a database and insert data into it.
This installation prompts the user to enter the SQL user and password. This
installation doesn't remember the SQL user and password anywhere.
I then created an MINOR UPGRADE installation to modify the
There is a type of custom action (resolves to type 18 and variations) that
specifically means run this exe being installed with the product as a custom
action. As long as you want to run it after the files are installed that's
fine, but I suspect you wouldn't be asking if that was the situation.
No. Windows says basically, oh, this is an MSI product so I'll just call the
appropriate Msi API call directly.
Phil Wilson
-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Monday, March 07, 2011 12:39 PM
To: General discussion for Windows Installer XML tools
This probably has to do with the fact that I have the element in
the .wxs but I notice that in the registry the UninstallString is the same as
the InstallString something like "msiexec -I{ABCDE}". The software doesn't
actually get uninstalled with this string I have to use (and the Add/Remo
How do I detect uninstall or minor upgrade or first time install. I looked at
the values in the table in the following article
http://stackoverflow.com/questions/320921/how-to-add-a-wix-custom-action-that-happens-only-on-uninstall-via-msi
and I don't think they are correct! Are they? Why do I n
I'm running a MSI install file to register DLL's on client machines. The
DLL's are located on a server share (same location that the MSI is
running from). So the DLL's will be registered to a network share e.g.
"\\server\apps\programs\xzip.dll".
How do you read the network path of where the appl
Hello,
I am in a situation where I need to use a file in a custom action that I am
also laying down as part of the file set stored in the cab build into my
MSI.
Is there a way to get that file out of the cab from a custom action? I know
I can include the file in the binaries table, but that woul
I'm trying to set permissions on a registry key so that it can be written
to without requiring elevation. I've got the following component:
I have successfully set permissions on other keys using similar code, but
this one isn't working. Aft
To enable Windows Installer logging
To enable Windows Installer logging yourself, open the registry with
Regedit.exe and create the following path and keys:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
Reg_SZ: Logging
Value: voicewarmupx
The letters in the value field can be i
Hello... Is there a setting in Wix to enable logging as always? Thank you.
--
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connec
Include fies (.wxi) are processed by the preprocessor. Library files
(.wixlib) are processed during linking. You need variables that happen after
linking, aka binder variables (WixVariable element).
On Wed, Mar 2, 2011 at 5:41 AM, MikeR wrote:
> Is it possible to reference a .wxi file that is in
1. Yes. Use conditions in the execute & UI sequences to determine if you
should execute the action (for example, at uninstall time).
2. If you store custom action dll in the binary table using the
element, the custom action is available as long as the installer is running.
3. Custom actions can us
Use a directory with an Id of 3RDPARTYPROGRAM_PATH. When the property with the
same name gets
updated so will the directory path.
Rob
On 04/03/2011 22:10, Mr Dimitri Klyachko wrote:
> I have a task to add a file to a directory that appears after the 3rd party
> software has been installed.
>
19 matches
Mail list logo