I'm having a hard time trying to understand or find an example on how
exactly upgrades of merge modules work. Do I have to program this all
myself?
Basically I am distributing a third party library, and I want consumers
of this library (those who merge it in) to install it only if it doesn't
exist
> That level of control isn't possible in a merge module. Provide an .msi
> package instead.
So, what's the point of merge modules then? If I can't distribute a
third party library that other people can use as a dependency, what good
are they for?
And I don't think one can reasonable say it can
Hmm... you mean I have to write a piece of software to install the
dependencies before I run the installer? Wonder if I can just do this
with NSIS or InnoSetup or something.
On Wed, 2007-05-30 at 06:31 -0700, Bob Arnson wrote:
> Jerome Haltom wrote:
> > So, what's the point of merg
That doesn't really explain what the bootstrapper is. What is this
bootstrapper thing? How do I build one?
On Wed, 2007-05-30 at 19:18 -0700, Bob Arnson wrote:
> Jerome Haltom wrote:
> > Hmm... you mean I have to write a piece of software to install the
> > dependencies before
> 1. I really wish
> http://msdn.microsoft.com/msdnmag/issues/04/10/Bootstrapper/ was more of
> a how-to. It isn't really intuitive on how to use all of this tooling in
> Visual Studio 2005, or where to find it.
>
> 2. WiX really needs a better bootstrapper as a part of what it offers.
> If it wer
uot;The
> Definitive Guide to Windows Installer" that minor upgrades and patches
> aren't possible with nested installs - again the servicing problem raises
> its ugly head.
>
> --
> Mike Dimmick
>
> -Original Message-
> From: [EMAIL PROTECTED]
Is there anyway to make a component that contains directories? I'd like
to attempt, if possible, to make a single component for my entire
package. It would certainly ease versioning (there is no way I am
keeping track of a dozen component Guids manually).
-
umentation about Components and the rules for updating their GUIDs.
> Managing the GUIDs is (unfortunately) a very important part of the Windows
> Installer development process.
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jerome Hal
priority is keeping the project running as smoothly as possible).
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jerome Haltom
> Sent: Thursday, May 31, 2007 10:10 AM
> To: Peterson, Joel
> Cc: [EMAIL PROTECTED]; wix-users@lis
compatible).
On Sat, 2007-06-16 at 10:59 -0700, Bob Arnson wrote:
> Jerome Haltom wrote:
> > As I deploy new versions of my merge module, and new third parties
> > include them, I may be removing and adding new files. These would result
> > in the components being removed and t
Thanks for all the help. I'm going with NSIS though, I suspect.
On Sun, 2007-06-17 at 21:29 -0700, Bob Arnson wrote:
> Jerome Haltom wrote:
> > Sure, but if my merge modules components are merged into the package
> > installers components, then a major upgrade of the package
unavoidable reason, I can just make a MSI file that
executes the NSIS file and only have to remember two guids.
Thanks for all your help, btw. Just can't waste any more time on this
stuff.
On Mon, 2007-06-18 at 17:24 -0700, Bob Arnson wrote:
> Jerome Haltom wrote:
> > Thanks for all
12 matches
Mail list logo
