Please keep /wix-users/ on the thread.
Igor Lemsky wrote:
But there are no subfeatures - try it yourself!
You're right -- MSI seems to always include the "entire feature" menu item.
--
sig://boB
http://bobs.org
-
Take Su
Bei Liu (Volt) wrote:
When use "AsyncWait" it didn't give error dialog. When use "check", it
gave the error dialog.
Which error dialog?
Error 1722
Then that means MSI got back a non-zero exit code. I've never seen any
other instance of a 1722.
Can you confirm if the following is the
David Roberts wrote:
Does this still work in Wix 3.0?
No, the SKIPCONFIGUREIIS hackworkaround wasn't part of v3 because v3
supports overridable custom action references:
MYCONDITION
--
sig://boB
http://bobs.org
---
Kevin Burton wrote:
> Thank you very much. Progress but I think I am running into the second
> problem that you mentioned. The documentation states that in order for the
> property to be set in the UI phase and passed to the execution phase it has
> to be public for Windows XP and Windows 2000. I a
Does this still work in Wix 3.0?
I've just tried this and from the logs I can see the property is set to
1, though ConfigureIIs still launches.
In Bug #1067343, Rob suggests:
"In WiX v3, custom conditions
can be provided for custom actions and we'll investigate
unwinding the code enough to do
The element is used in three places:
* To prevent an installation from proceeding - this is under the
or elements
* To set whether a feature is installed by default or not - under the
element
* To enable, disable, hide or show a control - under the
element
Many other ope
Hello all,
I'm a relative WiX newbie, so please forgive the newbie question. But I've done
a lot of research into this, and it seems to be a subtle thing. I'm aware of
the element in the WiX schema, and I have one that detects the
presence of .NET 2.0. But my requirements say that I'm suppose
It's been a while since I looked at this part of the code, but I don't think
you actually can set these attributes currently. If you have any thoughts on
how that could be solved feel free to make a suggestion... (Note that there is
the [EMAIL PROTECTED] attribute that makes a WiX provided CA do
Somebody else on the list hit this exact problem last week too...
Copy paste reply:
This is a known problem, see bug #1067343:
http://sourceforge.net/tracker/index.php?func=detail&aid=1067343&group_id=105970&atid=642714
The workaround is to set the property SKIPCONFIGUREIIS to "1" when you are n
The problem with auto generating WiX source code like that is that you very
easily end up breaking the component rules. Each file should belong to its own
component, and the GUID of the component must remain identical as long as the
file has the same name and target location. Solving this in an
Hello,
I have a problem with file associations - can you tell me please what I
am doing wrong here:
ASSOCIATECSS=1
The file icon is not set and the association does not
11 matches
Mail list logo
