INSTALLLEVEL defaults to 1, and isn't changed until after CostFinalize when
initial feature states are computed. You would need to instead send the
AddFeature event targeting Product_Full instead of (or in addition to)
changing INSTALLLEVEL.
-Original Message-
From: Joel Phelps [mailto:joe
Ok,
I've seen around the web this is a good place to ask questions about
WiX. I have been working on an install for one of my company's
products. I've run into a couple of issues that I have not been able to
figure out.
1. When selecting custom install, this brings up the feature tree with
all
The short answer to this is that there is a DisableRollBack action, and a
property (uppercase) that you can set.
The right answer to this is that you shouldn't be using it. The real problem is
that you have a Wait setting in the ServiceControl element that makes the
success of your service sta
1st step: try to not use them.
2nd step: try to find newer/fixed versions of them.
3rd step: Reorder the MSMs so that one with a good definition (if any) is
consumed first.
4th step: fix the bad/broken column definition in the schema of
whichever/all MSMs wherever it's incorrect (this is the "hacki
It's the VC_User*.msm files that appear to be bringing the Class table
to the party. 5 of them all told. I'll have to check with the dev lead
and see if those are still needed. Might be, since we have a lot of
legacy code in our product. If so, is there anything to be done about
that? I'm guessing
Another thing that sometimes helps is to run a repair and then another
uninstall attempt.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Friday, July 30, 2010 9:15 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: RE: [WiX-users] Uninstall Error: Failed
I do use a couple of scoops of VC merge modules and one or two others.
Like this. I'll open each MSM in Orca and see if there's something
there.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Friday, July 30, 2010 9:21 AM
To: 'General discussion for Windo
Unlike some other authoring systems, WiX doesn't generate Class tables by
default. Are you using any MSMs?
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Friday, July 30, 2010 7:43 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re:
The error is likely to be between the middle and the end of those "thousands
of lines". It may also be productive (and even beneficial to the entire
community) if you open a case with Microsoft Support and send them the log
(or even that portion of the log). Maybe there is something they can tell
y
I do see a Class table with a Feature_ column, but it's a completely
empty table. No data rows at all showing in Orca. I looked at some of my
other installers and they don't have a Class table at all, even though
they do have several features similar to this one. I did not purposely
author a Class
Firstly don't use TARGETDIR as a ConfigurableDirectory as TARGETDIR is
the root element of your directory tree & used for other things such as
administrative installations (see ->
http://msdn.microsoft.com/en-us/library/aa372064.aspx). You main issue
seems to stem from confusing TARGETDIR with INST
The PATCH property is set during patching.
http://msdn.microsoft.com/en-us/library/aa370576%28v=VS.85%29.aspx
so something like "and not PATCH" might work for you.
-Original Message-
From: WiX_Maik [mailto:maik.czym...@de.bosch.com]
Sent: 30 July 2010 13:42
To: wix-users@lists.sourcefor
Hi! Thanks for your reply. I have now created a patch successfully, but when
I run the patch the installation runs into the "Maintenance Mode"
(Condition: "Installed AND NOT RESUME AND NOT Preselected"). Is there a way
I can figure out if the current "Mode" is PATCH or something like that as a
con
You cant remove components in a patch. You need a major upgrade to do
that. There is a workaround called the "puncture pattern", mentioned
here if you really need to do it but you can just leave the component in
place until the next major upgrade.
http://geekswithblogs.net/Vagmi.Mudumbai/archive/20
Dear community,
I want to create a Patch (MSP) for an existing MSI Setup package. Therefore
I use the "diff" between my currently released MSI and the new one I
have/want to create. I understand how to update existing components of my
initial MSI package, but how can I add new files or remove com
The only difference is one is named INSTALLDIR & the other is named
INSTALLLOCATION.
It's the same as doing
string xyz;
string abc;
It matters not which you choose just make sure you're consistently using
the same one or you'll trip yourself up. MSDN page on Properties is ->
http://msdn.microso
You could find out what's causing the problem & fix it as those modules
uninstall completely fine for hundreds if not thousands of other peoples
products without any issue so it's highly likely the problem is being
caused by your installer code.
Or you could remove the consumption of the VC++ merg
Hi ,
In my installer I am installing windows service. If the service fails
to install or start my installer roll back all the installation. Can
anyone let me know how to proceed or complete installation though the
service fails.
This is my wix code
18 matches
Mail list logo
