I finally figured out what was going on. The documentation mentions you can
just copy the WiX file and change the filename and the Id of the UI
element. This works just fine for WixUI_FeatureTree, WixUI_InstallDir,
WixUI_Minimal and WixUI_Mondo. However, WixUI_Advanced also declares
several
On 25-Apr-11 11:15, Dave Combs wrote:
My simple solution was to change the name of these custom actions in my copy
(to KzSetDefaultPerUserFolder, etc.) and to any references to them, without
changing their contents.
You could also just delete your copy of them and reuse the ones in the
It might be a very recent installer error. The SDK docs go to error 2621 for
MSI 4.0. Versions 4.5 and 5.0 may have added new values that appear to be
undocumented. You wouldn't see a non-Windows Installer error in the context of
that message string either, and that's another clue it's new
Sounds like this famous bug again. This applies to anything installed by
Fusion, including the VC merge modules on Vista and above (in SxS).
http://support.microsoft.com/kb/905238
Phil Wilson
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Wednesday,
FWIW, I've come across customers who are not happy about installs that do this
kind of thing, including silently adding roles also. For example, reconfiguring
the customer's OS to add the IIS role because your app needs it is something
that the customer should have a say about. Non-HTTP
Hi to all,
This might be an old question. Eventhough I have been searching for
examples. I have 2 msi files one for x32 and the other one for x64. I could
manage to verify if the system is NT64 or not and based on that setup the
installer. When the Installer runs the Install_MSI_x64 custom
Orlando,
I don't see the screen (you can;t attach screen shots to forum posts
sdaly hence why it may not show up) so I don;t know what error you are
seeing.
However, if you are suggesting that you run one installer from another,
then Microsoft advise strongly against it. If you need to run
I checked and it is installing correctly the msi (If is windows XP it copies
the x32.msi file to Program Files else it copies the x64.msi to Program
Files). After that I tried running the x64.msi.
the screenshot is like if I run the command [msiexec /h] in command
prompt... you get this screen
I'm trying to use the WixUI_Advanced dialog set as a starting point, but
replacing various dialogs and adding others of my own. When I specify
AdvancedWelcomeEulaDlg, things compile and link okay. When I try to change
that to LicenseAgreementDlg instead, I get an error
error LGHT0094 :
Is File Id=filDADA6C31C211881DDF89BEAE6A9B7A1A/ in the same Component as
the registry entries you provided below?
Blair
-Original Message-
From: Shashikant Saini [mailto:shashikant.sa...@imail.org]
Sent: Monday, April 18, 2011 3:31 PM
To: wix-users@lists.sourceforge.net
Subject:
From the history.txt files:
BobArnso: SFFeature:3130590 - Update DifxApp DLLs in DifxApp .wixlibs to
version shipped in DDK 7600.16385.1.
Introduced in the following builds:
3.5.2430.0 3.6.1230.0
This newer build of DifxApp is not in any 3.0.x build of WiX.
There were some
Please file a feature request so it doesn't get lost in the email list.
Blair
-Original Message-
From: Alex Ivanoff [mailto:alex.ivan...@shavlik.com]
Sent: Thursday, April 21, 2011 7:18 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Integrity of
Depends on when your custom action is scheduled. Can you describe in more
detail what you are trying to achieve?
Blair
-Original Message-
From: Rune Moberg [mailto:jjfl...@gmail.com]
Sent: Saturday, April 23, 2011 1:18 PM
To: General discussion for Windows Installer XML toolset.
For heat, -ag uses the * value to generate stable component guids. -gg
is only useful for running heat once to get a WXS structure that you will
maintain manually (or programmatically but not using heat).
If you have not yet released your MSI and you need to use heat in your
build, use -ag not
If my math is still working this late at night, 4608 = 512 + 4096. 4096 =
msidbFileAttributesPatchAdded. That attribute must only be present on a file
that a patch added (i.e. that is not present in the MSI) according to
http://msdn.microsoft.com/library/aa368596.aspx. Which patch is adding that
15 matches
Mail list logo
