No bootstrapper involved. I can apparently make redistributable NSIS
files and just have another NSIS file run it silently. Which works just
fine. Also, no need to remember guids or the rest of that weird esoteric
stuff that windows installer seems to favor. And if I *really* need a
MSI for some un
Jerome Haltom wrote:
> Thanks for all the help. I'm going with NSIS though, I suspect.
>
Um, OK, but how's that any different than creating an MSI (instead of an
MSM)?
--
sig://boB
http://joyofsetup.com/
-
This SF.net
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, which ended
> > up us
Jerome Haltom wrote:
> Sure, but if my merge modules components are merged into the package
> installers components, then a major upgrade of the package, which ended
> up using a different version of my merge module, would result in the
> components in my old merge modules being unreferenced and re
Sure, but if my merge modules components are merged into the package
installers components, then a major upgrade of the package, which ended
up using a different version of my merge module, would result in the
components in my old merge modules being unreferenced and removed if
those same component
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 the ref count being decreased,
> correct? In which case, upgrading a third party from library Ve
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
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]
possible with nested installs - again the servicing problem raises
its ugly head.
--
Mike Dimmick
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jerome Haltom
Sent: 30 May 2007 03:13
To: Bob Arnson; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] up
Sent: Thursday, May 31, 2007 9:45 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED];
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] upgradable merge modules
Couple comments.
1. I really wish
http://msdn.microsoft.com/msdnmag/issues/04/10/Bootstrapper/ was more of
a how-to. It isn't really
I've got some preliminary notes/sample code/links about how to actually
create a bootstrapper here that could be of help:
http://mindcapers.com/wiki/Bootstrapper
It's under construction, so a bit of a mess, sorry.
Julie Campbell
[EMAIL PROTECTED]
_
EMAIL PROTECTED] On Behalf Of Jerome Haltom
Sent: Thursday, May 31, 2007 10:10 AM
To: Peterson, Joel
Cc: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] upgradable merge modules
> 1. I really wish
> http://msdn.microsoft.com/msdnmag/issues/04/10/Bootstrapper/ was more
Yeah, I agree that MSDN article really doesn't say much about how to do
it... I should probably have read it better before passing on the URL,
it was just one of the early results in the Google search I did!
As far as the better bootstrapper is concerned, I believe that is part
of the vision for C
ginal Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peterson, Joel
Sent: Thursday, May 31, 2007 9:45 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] upgradable merge modules
Couple comments.
1. I really wish
> 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
Bob Arnson
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] upgradable merge modules
That doesn't really explain what the bootstrapper is. What is this
bootstrapper thing? How do I build one?
* C O N F I D E N T I A L I T Y N O T I C E *
-
bject: Re: [WiX-users] upgradable merge modules
That doesn't really explain what the bootstrapper is. What is this
bootstrapper thing? How do I build one?
* C O N F I D E N T I A L I T Y N O T I C E *
---
The content of this e-mail i
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 I run the installer?
Jerome Haltom wrote:
> Hmm... you mean I have to write a piece of software to install the
> dependencies before I run the installer?
No because ideally the bootstrapper gracefully handles both your prereqs
and the product installer itself.
--
sig://boB
http://joyofsetup.com/
---
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 merge modules then?
Jerome Haltom wrote:
> 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,
>
You can, just not with the arbitrary upgrade functionality you want.
> If I provide a .msi file, how will their .msi file include it?
>
> 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
Jerome Haltom wrote:
> I'm having a hard time trying to understand or find an example on how
> exactly upgrades of merge modules work.
That's because they don't. Upgrades are the domain of products, not
merge modules.
> Basically I am distributing a third party library, and I want consumers
> o
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
24 matches
Mail list logo
