Hi
1. Is it possible to uninstall just a single instance, if that instance is
no longer needed?
Yes, Add/Remove programs will do it, or you can use the command line if you
know the Instance ProductCode
2. Is it possible to upgrade just a single instance, if needed.
Yes, but again you need some
As I am sure you have read, multi-instance can be a painful road, but YES it
is possible to do both of the above.
Each instance will just need to make sure to have it's own product codes and
upgrade codes. Then they can be upgraded or uninstalled independently of any
other instance on the system.
I have a requirement to add the ability to support multiple instance
installs to our website Wix installer. I've been looking at a few sites that
discuss how to do this, but I have a couple of questions regarding this.
1. Is it possible to uninstall just a single instance, if that instance is
no l
Hi,
Package A ist installed conditionally (e.g. based on user selection) and
requires Package B. So Package B should be installed only if Package A
is installed.
Of course this can be achieved with the mba, just wondered if there's a
cleaner solution.
Michael
Am 09.06.2011 20:03, schrieb John
Sorry for my previous empty post. Must've got sent by accident.
Thanks, Peter, for your ideas. I’ll consider them.
>>Cant you just upgrade the older installer with the fixes to A, keeping B
as it was at release, and make that available to old users for download?
The old installer (pre-2010) did n
Hi,
Are you talking about A.MSI must be installed before B.MSI?
If so use the After attribute on the MSIPackage Element when defining B.MSI in
your Burn WXS files. See
http://wix.sourceforge.net/manual-wix3/wix_xsd_msipackage.htm for more info.
John
Wintellect
http://www.wintellect.com
+1-877
Here is the markup. Thank you for your help.
Test Environment:
Windows Server 2008 R2
IIS 7.5
.NET 4.0
--
View this message in context:
http://windows-installer-xml
Thanks Peter!
I will only rearrange the feature/component tree. File will not be moved to
another location.
So major upgrade will be it.
Thanks again!
Martin
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Thursday, June 09, 2011 5:45 PM
To: General discus
You should not change the guid when moving between features.
You would change it if you moved the component to another directory, which is
what you might be thinking of.
If you rearrange the feature-component tree then you can only use major
upgrades. You won't be able to create a small or minor
Hi,
I have one component that I need to move from one feature to another.
Should I change the component GUID in order to prevent orphaned files?
Thanks,
Martin Kulov
http://www.
What't the WixDependencyExtension? Any documentation on it?
I'm looking for a way to tell burn that package A needs package B
installed. Can this be done with WixDependencyExtension?
Michael
--
EditLive Enterprise is th
Hello everyone,
this is my first participation in the mailing list - do forgive my
(hopefully) trivial questions!
What I need to do is this:
- 4 data files should be extracted to a specific (but "user-relative")
location.
- the user should decide which of the 4 files that should be extracted
(chec
Cant you just upgrade the older installer with the fixes to A, keeping B as
it was at release, and make that available to old users for download ? Then
make a later version of that installer with the new version of B and make
that available for new users on CD.
If you don't want to make an upgrade
13 matches
Mail list logo
