Well no not really. I just need to install a component differently on 64 than
on 32. Specifically I want the component to be permanent on 32, but not on
64.
I think I can get around this by having two versions of the same component,
and then for the 64 bit one, rename (CopyFile) it to the
Igor Lemsky wrote:
Previously I mainly use major upgrades with changes of product codes.
Now I need minor upgrades which allow more soft upgrade - just
reinstall and also allow patches. Major upgrades for some strange
reasons doesn't allow it.
Don't allow what?
You're right that removing
Neil Sleightholm wrote:
In
the online help there is this paragraph: "You can most easily add
and remove dialogs from the stock dialog sets by copying one of the
existing sets and modifying it. For an example, see the project in the
doc/examples/wixui/custom directory."
This
Dana,
I think the better way is try to use FindWindow, since we always know
the name of the MSI dialogs we use and all MSI dialogs have same class
name - MsiDialogCloseClass. But I have no chance to try this way yet.
Best regards,
Peter G. Sakhno
C-MAP RUSSIA Ltd
http://www.c-map.ru/
Dana
Peter:Thanks for the suggestion, I just tried HWND hWndParent; hWndParent = FindWindow(_T(MsiDialogCloseClass), NULL);This seems to work very well. I haven't noticed any times (yet) where my dialog is behind the MSI main dialog.
Thanks,DanaOn 6/22/06, Peter G. Sakhno [EMAIL PROTECTED] wrote:
After doing this, does anything need to be recompiled?
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Thursday, June 22, 2006 12:13 PM
To: Neil Sleightholm
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Customizing dialog sets
The WiX Tutorial covers some of this but the process I
used:
1. Copy all the files in src\ui\wixui to a
newfolder
2. Copy src\ui\wixui\mondo\WixUI_Mondo.wxs (or which
ever base file you want) to the same folder.
3. Rename WixUI_Mondo.wxs and edit it to add/remove the
features you want.
4.
I read something in the history file about
support for a newer release of the SDK being added (BobArnso: Add support for Windows
2003 R2 Platform SDK), so you may want to make sure you are using the
latest build.
Frederik.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sam
I
ran intothe sameissue 2 builds ago - tried changing the GUID to the
new one used by the latest SDK but had further downstream errors and gave up.
The latest build is successful with the R2 SDK so you should be good to go
now.
HTH
Subbu
-Original Message-From:
[EMAIL
9 matches
Mail list logo