I know there is probably a posting somewhere out on the web describing the
issue I am having, but I am not able to find it at the present moment.
The problem I am current having is that the 64 bit version of MS build does not
properly evaluate the build variables and is not able to find WIX
I am using WIX 3.8 (build 3.8.708). The build system is using the GA version
of WIX 3.7.
I am havine issues on both systems.
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: Tuesday, August 27, 2013 10:37 AM
To: General discussion for Windows Installer XML toolset.
-Original Message-
From: Skildum, Mathew [mailto:mathew.skil...@aspect.com]
Sent: Tuesday, August 27, 2013 10:44 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset
I am using WIX 3.8 (build 3.8.708
, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: Skildum, Mathew [mailto:mathew.skil...@aspect.com]
Sent: Tuesday, August 27, 2013 11:38 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit
-users@lists.sourceforge.net
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset
On 8/27/13 10:05 AM, Skildum, Mathew wrote:
Here is an example of the build errors:
CustomAction.cs(4,17): error CS0234: The type or namespace name 'Deployment'
does not exist
:0ptikgh...@gmx.us]
Sent: Tuesday, August 27, 2013 1:13 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset
On 8/27/13 11:03 AM, Skildum, Mathew wrote:
All hint paths are correct as everything build correctly in Visual Studio
I am currently working on implementing a multiple instance MSI base
installation using WIX and am trying to validate that patching will work
correctly before I go any further. I have been able to create a patch that
updates all instances exactly as I would suspect, but when I try to install a
to get right, adding the patching
on top of it can become real confusing rather quickly. Other than that, there
isn't much we could do without the command line / logs from when you are trying
to apply the second patch (the failing one).
-Original Message-
From: Skildum, Mathew
Does anyone have a way to extract embedded transforms from the _storages table
in MSI?
I know you can do it with Msidb.exe, and I have read you can do it through OLE
structured storage APIs but have not found any examples on this method as of
yet.
Any pointers in the right direction would
Everyone,
I have a multiple instance install that I am working on and ran into an issue
doing upgrade testing. It looks like all instances are removed when one of the
instances is upgraded. This looks to be because WIX does not allow for the
UpgradeCode to be modified in the instance
This method only hides the value of the property when it is directly printed in
the log file. If you pass the property to a deferred custom action, it will be
visible in plain text once again in the custom action data property.
You either need to mark all custom action data properties as
This process will not generate the same GUIDs and other identifiers you need
for patching. It will only generate a unique usable WIX fragment you can
include.
You can use this for upgrades as you do not use component GUIDs as much in the
upgrade process, but if you want to support patches you
I do this by presenting a dialog to the user and they can choose which option
they want. I then have a single action on the back end that sets up the
correct ADO.Net connection string based on the users choices.
By doing this you are not duplicating code, you just have a minor detour is SQL
You can remove a component during a minor update, but it is not recommended as
you are orphaning the file(s) when the product is uninstalled.
I have done this when it is absolutely necessary, it just takes adding the
correct remove file entries to clean things up correctly.
As with any change,
I have multiple custom actions the access SQL server through OLE .NET and
occasionally I will get a rundll32 error that pops up on the screen. The popup
looks to come from Ole .Net process running the SQL scripts and not directly
from the install itself. The actual error code is RUNDLL32
I know this may be covering the same ground as previous discussions, but I just
had the legal team of my company look at the license that is shipped with the
WIX 3.6 tool set.
According to the way the license reads you must ship the source for DTF along
with every installation that uses this
You may want to check the values in the Upgrade table. It sounds as though the
existing values do not cover the installation you are trying to upgrade. Pay
specific attention to the listed upgrade codes and the version settings.
Mat Skildum
-Original Message-
From: Ian Brooke
By default when a new sub feature is added it is automatically enabled if the
parent is enabled. This is the way MSI has always functioned in my experience.
I do not know where this functionality is documented.
It is always best to add new files to existing features so that you do not have
MSI does not support directly support what you are trying to do with text
boxes. You can do this sort of thing with radio buttons and check boxes as
they cause the MSI engine to evaluate the dialog when used. A text box or
other text controls do not cause this behavior so your button will
I recently started looking into Dark and how it functions, but I cannot find
any examples of how to do custom UIs except for the WIX 3.6 install. I have
downloaded the WIX 3.6 source code and am in the process of working though how
the UI works in this case.
Are there any other good examples
-Original Message-
From: Skildum, Mathew [mailto:mathew.skil...@aspect.com]
Sent: Tuesday, December 27, 2011 7:12 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Custom UI examples for Dark
I recently started looking into Dark and how it functions, but I cannot
The main problem I see here is your versioning scheme. MSI only supports the
first three places in the version number (X.X.X) and ignores the fourth
position. Any version changes need to take place in the first three positions
for MSI to recognize a version change. For more information
Registry entries in the MSI are only updated when the file they are linked with
are updated.
The easiest way to handle this situation is to have a custom action that
updates the targeted registry value when the patch is run.
Mat Skildum
-Original Message-
From: Michael Tissington
I had similar issues using the Crystal merge modules.
This problem is because the dependencies the Crystal runtime DLLs have on the
Microsoft MFC framework for the targeted version of Visual Studio. You need to
make sure that the needed runtime is installed ahead of time, so that when the
You can do this yourself by using the upgrade table and to check for the
product version you are looking for and only set the property. You can then
use this property to set an installation condition to display a message that
the pervious product must be manually removed before continuing.
Is the problem on a 32 bit or 64 bit system?
Make sure the registry search matches the bit level that was set for component
containing the initial registry write.
-Original Message-
From: yheip p [mailto:zyhp...@gmail.com]
Sent: Tuesday, July 05, 2011 5:51 AM
To: General discussion for
I have run into an interesting issue with some of my rollback custom actions.
I usually test this support by canceling the install at a set point and
normally my actions fire with not error. But today I ran into an issue where
my action enters but it catches the
you,
Miaohsi
-Original Message-
From: Skildum, Mathew [mailto:mathew.skil...@aspect.com]
Sent: Tuesday, May 17, 2011 8:58 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to cache msi for Modify/Repair to use
There is no generic way to do this, You
There is no generic way to do this, You will basically have to write your own
custom actions that does this task and updates the source list for the MSI
package.
I personally created a merge module with a set of actions that cache the MSI in
a set location and handle any cleanup and
There is no runtime or build time solution to replace installutil.exe.
The only options are to extract the registry entries that are created and
include them in the project or running installutil.exe at runtime. The best
option is to extract the registry either by having InstallUtil create a
Currently I am having problems registering a WMI interface during a product
upgrade. Currently I am using a custom action to directly access the exported
functions in the file InstallUtilLib.dll. Everything functions as expected
on a new install but when the product is upgraded but the wrong
The best way to do this is to query the Win23_ServerFeature namespace through
WMI in a DTF custom action.
Every Windows feature has its own ID that can be searched for.
The only restriction I have found with this method is when UAC is enabled. The
install must be running with elevated
The is achieved by enabling the install to support elevation. MSI does this by
default when UAC is enabled and you are targeting the 4.0 or higher MSI engine.
There are two things you need be aware of when using custom actions:
1. All immediate custom actions run in the current users
No you cannot.
You must use a valid version string for the file versions. MSI requires this
to be able to do a version compare when needed.
You can put this information into the Product version file of the file
assembly, but not into the File Version.
Mat Skildum
-Original Message-
This is a generic failure error. You need to hunt through the log an find the
exact place the install failed. Usually it is a result of custom action
failure.
Mat Skildum
-Original Message-
From: swapna.rachako...@thomsonreuters.com
[mailto:swapna.rachako...@thomsonreuters.com]
This is actually a function of MSI not WIX. WIX is just the mechanism to build
the MSI where the rules are enforced.
MSI does follow these guidelines as far as I know. When you put the UAC shield
on a button that does not mean the elevation request will happen right away.
MSI does this
[mailto:br...@cran.org.uk]
Sent: Thursday, March 24, 2011 8:19 AM
To: General discussion for Windows Installer XML toolset.
Cc: Skildum, Mathew
Subject: Re: [WiX-users] Query about use of UAC shield on Install button
On Thu, 24 Mar 2011 13:07:30 +
Skildum, Mathew mathew.skil...@aspect.com wrote
To: Skildum, Mathew
Cc: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Query about use of UAC shield on Install button
On Thu, 24 Mar 2011 13:26:05 +
Skildum, Mathew mathew.skil...@aspect.com wrote:
Using the UAC shield is completely up to you not WIX. Since WIX
You should set Remove=Both in your service control entry.
This will help in the cleanup and if any other service happens to share the
same name, you remove it.
Mat Skildum
Aspect Software
direct: 630.227.8534
mobile: 847.909.9921
mathew.skil...@aspect.com
-Original Message-
From:
You have to use a custom action to do what you are trying to do.
For example:
CustomAction Id=SetMACHINENAME Property=MACHINENAME
Value=[ComputerName] /
Mat Skildum
-Original Message-
From: kim [mailto:contactme...@gmail.com]
Sent: Thursday, March 24, 2011 2:49 PM
To:
Would the version of the MSI engine you are targeting play a part in what
happens. If you are not targeting the 5.0 version of the engine, this may not
function as expected.
Mat Skildum
-Original Message-
From: Dick Van den Brink [mailto:d_vandenbr...@live.com]
Sent: Tuesday, March
You can also force a true Administrator check in you install (set the property
MSIUSEREALADMINDETECTION) if you do not have time to work around UAC.
Mat Skildum
-Original Message-
From: The Eligible Bachelors [mailto:theeligiblebachel...@yahoo.com]
Sent: Tuesday, March 15, 2011 11:04
In cases where you checking things like credentials you want the actions to
return success so that the install does not fail. As it was said, you set a
property if the call succeeded and check if the property is set.
You use the other return values in those cases where you want the install to
But I want the install to fail. If it continues with the wrong credentials it
will try to start services with the wrong credentials.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Skildum, Mathew
In those cases where you require a newer version of the MSI engine than what is
installed, you will have to have a prerequisite installer in place to check for
and install the required MSI engine.
Mat Skildum
Aspect Software
direct: 630.227.8534
mobile: 847.909.9921
mathew.skil...@aspect.com
Unfortunately there is a completely different set of APIs for working with IIS
7.
Here is the link to the MSDN documentation on the ServerManager Namespace:
http://msdn.microsoft.com/en-us/library/microsoft.web.administration.servermanager(v=vs.90).aspx
Mat Skildum
-Original Message-
For this to function you will need to make sure your install supports UAC and
elevated privileges as the target OS would be Vista or higher to see this type
of behavior.
You need to make sure the all deferred custom actions have the value
Impersonate=no set. This will force them to run at the
47 matches
Mail list logo
