Hello everyone,
Does any one has any update regarding this issue?
Thanks in advance.
with regards,
KD
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/bootstrapperApplicationData-attribute-is-not-declared-tp7595444p7595956.html
Sent from the
I don't understand what is meant by:
If I add new project in existing project where I add reference of other
project to create msi path, its not compiling and giving mentioned error.
--
View this message in context:
This could be a simple question, but at the moment I just can not see it...
For push buttons and check boxes we just add the amp; in front of the
character that we want set for controls Alt hotkey, but if you have Edit and
MaskedEdit controls how do you set it's controls Alt hotkey?
Thanks.
Why would you want to and what would you expect it to do? For buttons and check
boxes they perform the command associated with the control, for an edit control
it just doesn't make sense to do so.
-Original Message-
From: TimM [mailto:timmay...@smarttech.com]
Sent: Friday, July 18,
It was a request from one of our managers as they noticed that they can use
Alt-Hotkey on the Change Directory dialog box, even though this is a
built-in MS dialog box. But that dialog box can do it so they wanted in in
the main installer as I have a Custom Dialog box that has 5 edit controls
and
To be clear, it's not a question whether WiX supports it. It's a question
whether the Windows Installer supports it. Did you try setting the hotkey in a
static control with tab order before the edit box. That's the way you typically
handle it in Win32 dialog boxes.
No I have not tried that so I'll give it a try.
Thanks.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Custom-Dialog-box-edit-controls-and-setting-Alt-hotkeys-tp7595958p7595962.html
Sent from the wix-users mailing list archive at Nabble.com.
Due to lack of foresight and inexperience when I was new to WiX, I've gotten
myself the following problem:
I have 2 product installers, A B. Each contains 2 DLLs, X Y.
A always installs both X Y to folder M
B (optionally) installs X to M and Y to another folder, N
A is a released product and
I wouldn't search. Just include Y in two different Components in B and ensure
the Guid for the Y Component in B matches the Guid for the Y Component in A and
give the Y Component to N a different Guid.
___
FireGiant | Dedicated
Are you using Burn to deploy your install? If so it seems like you'd want to
create a patch for your A install and distribute it with the B bundle. Even if
the feature isn't currently selected, the patch would update it such that if
they went to modify A and chose to add the feature that it
Okay thanks Rob that did the trick. I had to make sure the static text
controls had Tabskip set to 'no' though to get it working. But all good
now
--
View this message in context:
Among many perfectly fine working shortcut defs I have the one below
(strings modified to protect the innocent, but length of strings is preserved)
Shortcut
Id=SHORT_MessageCenterShortcut
Name=xx Notification Center
Description=xx Notification Center
Is it that you are shortening it or that Name != Description.
Wix only makes MSI easier. MSI only creates the shortcuts, Windows is
responsible for displaying the shortcuts (and their descriptions).
I suspect you'd see the same behavior if you created the shortcuts manually in
your start menu.
Thanks Jacob,
had tried 'lengthening' entries in the menu to rule that out, but apparently I
must not have gone
wide enough. Windows is indeed the culprit - once you are too wide, it displays
both Name
Description in two lines for some silly reason.
Still wish that WIX would give me a
14 matches
Mail list logo
