[wix-users] Advice needed

Sun Nov 15 14:57:44 PST 2015

Wix toolset (wixtoolset.org) is very different from wix the website builder. Not releated at all.  Do you remember signing up to a mailing list?  Typically there is a link in the invite/intro e-mail that you use to remove you from the list.

FireGiant is the maintainer of the mailing list so try to contact them: https://www.firegiant.com/. They should be able to remove you.  It may take a few days for them to get back to you.

Wes

________________________________________
From: wix-users <wix-users-bounces at lists.wixtoolset.org> on behalf of Geoffrey Fulton <thearchitect at internode.on.net>
Sent: Sunday, November 15, 2015 3:40 PM
To: 'WiX Toolset Users Mailing List'
Subject: Re: [wix-users] Advice needed

Somehow, I am receiving a lot of emails like this which has nothing to do
with me. What do I do to get rid of them for good? (I do have a Wix site)
Thanks!

ARCHITECTS FULTON +    SALOMON
ARCHITECTS,  INTERIOR DESIGNERS,  YACHT DESIGNERS,  PROJECT MANAGERS.
5 Loch Lomond Crescent, Torquay, Victoria 3228, Australia
Telephone: +61 (03) 52 619 422   Fax: +61 (03) 52 619 423  Mobile: 0438
619424
Email:   thearchitect at internode.on.net
www.containerarchitecture.co

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of
Colin Sim
Sent: Monday, 16 November 2015 5:16 AM
To: WiX Toolset Users Mailing List
Subject: Re: [wix-users] Advice needed

Using a bundle is a great idea, offering plenty of options to customise your
install. The only downside to using a bundle (.exe) is that as-far-as-I-know
it cannot be deployed using Active Directory, which may be an issue for
deploying in an enterprise.

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of
Phill Hogland
Sent: Sunday, 15 November 2015 9:11 a.m.
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] Advice needed

I am relatively new to both also, having started down the path of converting
years of legacy setups about two years ago.  The approach, advised here by
some, which has worked well for me is to stick to MajorUpgrades, but create
a Burn driven bundle of chained MSIs, which are small and contain the
functionality of a product's "feature" ( an application or group of
functionality).  I divided the significant groups of applications into
individual MSI packages (without any UI).  The Bundle has the UI, and
controls which packages are installed, etc.  I do not try to select MSI
'Features' per say.   The default  WixStdBA can be used, but eventually I
developed a managed BA using the WixBA in the wix source code as an example
project (although it is not a tutorial).   The WixBA is also an example of
using Web-deployment with packages which are built as part of the bundle
chain, but are staged external to the bundle on a web server.  The
web-connected user only needs to download the
 bundle (~1mb).  For an isolated deployment the Burn -layout switch is used.
So for an 'upgrade' I just build and stage a new Major Upgrade of the bundle
and each MSI package that is related to the bundle.  If a particular MSI
package did not have changes it is still part of the build and staging.  At
install time the Burn bundle knows to download only the packages which
aronly needs to update on package in the chain, or is a first time install.
It also does not download platform specific or locale specific packages if
not needed.    Most of these ideas came from studying how the Wix Toolset
team structures the wix\src\Setup projects in the source code and from blogs
like:
http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/
http://stackoverflow.com/questions/11572508/how-to-do-major-upgrades-when-us
ing-burn-wix-3-6

And from searching the old wix forums (which remains a good silent resource
to search) http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/

Also I use the RelatedBundle element to create an 'addon' bundle that has
another MSI package that is only needed to be added into the base package
for certain business situations.  In a similar way one can create a related
bundle that has your minor upgrade/patch, and deploy it as a ReleatedBundle
"patch" to the base bundle (although I have not done this yet as I am not
ready to figure out all of the issues related to minor upgrades or
patching).  To allow me to do this at some point in the future I add the
following to each bundle I currently ship.
<RelatedBundle Action='Detect' Id='$(var.ThisBundle_RelatedBundleGUID)' />

Then if I decide to create an 'addon' the new bundle will have something
like:  (or similar variant for a patch) <RelatedBundle Action='Addon'
Id='$(var.BaseBundle's_ RelatedBundleGUID)' />

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of
Yavor Ivanov
Sent: Saturday, November 14, 2015 9:45 AM
To: wix-users at lists.wixtoolset.org
Subject: [wix-users] Advice needed

Hi all!

I am new to WiX and windows installer stuff in general :) I am developing an
application and need advice how to plan for updates. Here is my case. I have
an application that is around 10mb. Apart from the main application I have
around 60 mb of content. I have created a setup that installs it all.
So far so good. But now comes the tricky part. The application is far more
volatile than the content. Bugs get fixed, new features are introduced. I
want to make it easy on the end users and not make them download the entire
70mb installer every time I fix something. The content is far less likely to
change than the application. Can you advice me what's the best way to have a
single installer for the application and content, while allowing the user to
update the application and content separately? For the content I can use
minor or small updates, while for the application I plan using only major
updates.

Regards,
Yavor

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant
http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant
http://www.firegiant.com/ This e-mail contains IPFX information which may be
privileged or confidential and is intended for use only by the individual(s)
or entity named above. If you are not the intended recipient, note that
disclosing, copying, distributing or using this information is prohibited.
If you have received this e-mail in error, please advise immediately to the
e-mail address above and permanently delete this message and any
attachments. Please note that any views or opinions presented in this email
are solely those of the author and do not necessarily represent those of the
company. We monitor our e-mail system and may record your e-mails. Thank
you.

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant
http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/