BTW - this thing say "For .NET Apps". I hope that is not a strict req. I
need it for an MFC app also. Anyway, I will take a look.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, September 05, 2007 2:26 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Merge Module and Upgrade element?
Point taken... And, actually I agree. I don't want to have to do this.
First of all, there is way too much logic in there that I don't want to
have to worry about.
The problem is that tools like the "GenerateBootstrapper" task, are
poorly documented with very few examples being found on the web. And the
examples that you do find are so simple they are useless. At least, that
is what I have found (if you have better examples, please send me a
link).
And for what it's worth, I did say:
>I also tried running the msxml6-KB933579-enu-x86.exe from another
installer (using a custom action), but I keep getting the "Setup is
already running" message and I have to exit the install. If there was a
way around that, that would be acceptable too...
But I guess launching one installer from another was something that was
supported in installshield at one time, but no longer?
But I will look into this dotnetinstaller also. Thanks
From: John Vottero [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 05, 2007 1:50 PM
To: Robert Priest; [EMAIL PROTECTED]
Cc: wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Merge Module and Upgrade element?
I would be furious if I installed a product only to find that the
developer had taken apart one of Microsoft's installers, dorked it
around and rebuilt it into a Frankenstein of an installer.
I think you should use a bootstrapper to install the real MSXML6 and
then install your product. Search for "GenerateBootstrapper" to find
information on the generatebootstrapper task which is part of Visual
Studio 2005. Search for "dotnetinstaller" which is a free bootstrapper
builder.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, September 05, 2007 1:32 PM
To: [EMAIL PROTECTED]
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Merge Module and Upgrade element?
Also, I said an "<Update/>" , but I meant "<Upgrade/>
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, September 05, 2007 1:30 PM
To: [EMAIL PROTECTED]
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Merge Module and Upgrade element?
Thanks for the response, Bob.
Let me go further into what I am trying to do:
I decompiled the msxml6 msi and created a merge module for it. So far,
everything seem to work -
1. The dll get installed in system32
2. All of the registry entries happen correctly, so far as I can
tell.
3. An entry appears in the "add\remove programs" screen for
msxml6.
Now if I were to use my merge module to install msxm6 and someone tried
to install using the MS installer, I would be properly located and the
"Already installed" message would be displayed.
But the opposite is not true, If you install using MS's installer first,
then using my merge module, my merge module will not detect the already
installed version and you will end up installing again and having two
entries in "Add\Remove Programs" which is obviously not wanted. I think
that all that stems from not being able to have an <Update /> element in
my merge module.
Is there another way around that? Do I need to right some vbscript and
set a property or something to prevent install?
Anyway, I have attached my .wxs file for my msxml6 merge module. None of
the files are included except for that. I know Microsoft is saying "no
more merge modules". But that is just not working for us.
I also tried running the msxml6-KB933579-enu-x86.exe from another
installer (using a custom action), but I keep getting the "Setup is
already running" message and I have to exit the install. If there was a
way around that, that would be acceptable too...
Thanks.
Robert.
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 05, 2007 11:53 AM
To: Robert Priest
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Merge Module and Upgrade element?
[EMAIL PROTECTED] wrote:
- My merge module installs certain dlls and registers them all.
I want to detect if the current version or a newer version is installed
and just exit without installing.
I want to detect if no version or a previous version is installed and
install over it.
Basically the same functionality as an <Upgrade/> element.
How do you do that from a merge module?
You can't control upgrades from a merge module: That's the
responsibility of a product, not its constituents. However, if you
follow component rules with stable component IDs and GUIDs, you get the
above behavior "for free." MSI tracks components and will do nothing for
each component that's already installed.
--
sig://boB
http://joyofsetup.com/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
