stephan o'farrill wrote:
> But again, even when I need multiple .msi packages I will have to create them.
> At least it would be nice if I could use the same source code. (I.e.
> the same .wixproj and .wxs). In this case would it be possible to
> reference the difx_app_*.wixlib in dependence of the
Thanks!
> MSI doesn't support having a single .msi package target both x86 and x64.
But again, even when I need multiple .msi packages I will have to create them.
At least it would be nice if I could use the same source code. (I.e.
the same .wixproj and .wxs). In this case would it be possible to
little.forest wrote:
> NOT InstalledWIXUI_EXITDIALOGOPTIONALCHECKBOXTEXT AND NOT
Installed
Check your ControlCondition table in Orca.
--
sig://boB
http://joyofsetup.com/
--
The NEW KODAK i700 Series Scanners deliver
Nathan Stohlmann wrote:
> As a temporary panacea I've customized the dialog sequence to remove
> the WixUIValidatePath custom action and the related ControlEvents from
> InstallDirDlg but I'm really curious if anyone has any idea what is
> going on with this? Unfortunately I can't send along a copy
xubutian wrote:
> If I set the TabSkip flag in wix, then Control_Next for these two buttons
> become empty. But at run time, I still can use tab to change focus on all
> the buttons.
>
So WiX is doing the right thing, per the MSI SDK. Have you confirmed
that MSI supports what you're trying to
stephan o'farrill wrote:
> I am able to either generate 32 bit or a 64 bit driver installer. For
> convenience it would be nice to be able to combine those into a single
> binary.
MSI doesn't support having a single .msi package target both x86 and x64.
--
sig://boB
http://joyofsetup.com/
--
Hi,
I am able to either generate 32 bit or a 64 bit driver installer. For
convenience it would be nice to be able to combine those into a single
binary. I am using votiv from inside my driver project.
1. I wasn't able to find out how to reference the appropriate
difx_app_*.wixlib in dependence of
7 matches
Mail list logo
