Hi Martin,
Did you change the Product ID and the version number? Both of those have to
change to be called a major upgrade.
http://wix.sourceforge.net/manual-wix3/major_upgrade.htm shows how to integrate
a major upgrade into your .WXS file.
John
Wintellect
http://www.wintellect.com
+1-877-968-
Hi,
I have an MSI installer built few months ago. It used to work fine during
MajorUpgrade.
Today I signed the MSI with code certificate and also added one Merge Module.
However now my MSI file gets installed as a new product and does not upgrade
the existing installation as it used to do.
Pretty annoying, heh?
Out of the box? No.
Some custom tables and custom action / custom dialog work? Sure.
Here's an article describing something I created back in 2006 for a former
employer:
http://blog.iswix.com/2006/07/short-comings-of-launchconditions.html
---
Hi all,
My installer has several launch conditions setup.
It works at it should, checking one condition at a time, and giving the error
message configured.
I was wondering if there is any way to run them all, instead of sequentially,
and show all the non-compliant messages.
Thanks!
Caio
-
Hi,
Run bundle with the following command line args: setup.exe /q
/INSTALLDIR="c:\dfds safds \sadfds" /SomeOtherParam
Managed BA receives the following string for command line args:
"/INSTALLDIR=c:\dfds safds \sadfds" /SomeOtherParam
The space in the path causes invalid argument parsing in the BA
Hello
I am new to the world of msi and started learning about patching. I learned
that you can have incremental as well as cumulative patches. For example, I
can have a patch 1.2 which will update 1.0 or 1.1 to 1.2. This will be
cumulative, but if I have incremental patches, they will be 1.0 to
I'm not certain what your exact problem is, but looking at the schema
for the remove file table leads me to believe you are missing fields
that are not nullable.
I've used:
const string REMOVEFILES_VIEW = @"SELECT `FileKey`, `Component_`,
`FileName`, `DirProperty`, `InstallMode` FROM `RemoveFile`"
The scenario I am trying to handle is the cancel during uninstall. If I were
to just bomb the folder the rollback wouldn't work and it would delete the
folder anyway. I am going to try and see if I can pressure the team into
using 3.6. Don't know if it will be an issue or not. Initially t
Okay, I'm looking at the installer in Orca. I see that all the directories
declared in the modules have the package guid appended to them (e.g.
ASPdirectory0.1A39512D_87E4_4FD4_AEFC_88DE0E1C2536), but that's the same for
those that went to the right place and those that went somewhere else.
A
I understand maintaining the customers data but isn't the goal here to remove
it? Which I agree is against the rules normally but it would appear that is
what is wanted... Did I miss something?
Jon
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Tuesday, Octobe
After the discovery of the variable WixStdbaThemeXml from this mailing list I
set about looking at my own corporate theme. In my main wxs I set these two
variables:
My objective is really to set a background image and have the other items
overlayed, looking at t
Open the MSI up in Orca or Inst Ed and you might find that the directory IDs
in the merge modules have had Guids added to them. Ids in modules are
"modularised" to avoid name clashes.
-Original Message-
From: Mark Modrall [mailto:mmodr...@mzinga.com]
Sent: 04 October 2011 23:14
To: Genera
12 matches
Mail list logo
