Re: [WiX-users] Prerequisite check for per-user vs per-machine installation

2010-10-19 Thread Lisa Gracias 
>
> Does product B always install a particular component guid (or at least a
> narrow set)?


I went through the installers for the last couple of versions and it looks
like the component GUIDs stay the same. To be safe I posted a question on
the Product B message board asking about their GUIDs. They said they are
using Visual Studio to create their installer so they don't know how the
GUIDs are generated or whether they'll change later on.
Any idea what makes an auto-generated GUID change?
--
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly 
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Prerequisite check for per-user vs per-machine installation

2010-10-18 Thread Blair 
Does product B always install a particular component guid (or at least a
narrow set)?

-Original Message-
From: Lisa Gracias [mailto:lisathelugubri...@gmail.com] 
Sent: Monday, October 18, 2010 10:38 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Prerequisite check for per-user vs per-machine
installation

I am building an installer for Product A. Product A should not be installed
unless Product B is already installed. There are multiple versions of
Product B that are supported by Product A. Product B does not create any
registry entries. So instead I am checking for the upgrade code of Product B
in the Product A installer. This worked fine until the latest release of
Product B came out. Now Product B supports both per-user and per-machine
installation, whereas it previously supported only per-user installation.
Product A supports only per-user installation, so the upgrade code search
fails if Product B was installed per-machine.

How do I create a check for Product B that will work for the existing
version and future versions as well?

Here is the relevant portion of the log:

MSI (c) (84:D0) [18:56:01:143]: Doing action: FindRelatedProducts
Action 18:56:01: FindRelatedProducts. Searching for related applications
Action start 18:56:01: FindRelatedProducts.
MSI (c) (84:D0) [18:56:01:143]: FindRelatedProducts: current install is
per-user.  Related install for product
'{7124DD21-022E-4868-B9B3-B139C6BD8F77}' is per-machine.  Skipping...
Action ended 18:56:01: FindRelatedProducts. Return value 1.

--
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly 
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly 
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Prerequisite check for per-user vs per-machine installation

2010-10-18 Thread Lisa Gracias 
I am building an installer for Product A. Product A should not be installed
unless Product B is already installed. There are multiple versions of
Product B that are supported by Product A. Product B does not create any
registry entries. So instead I am checking for the upgrade code of Product B
in the Product A installer. This worked fine until the latest release of
Product B came out. Now Product B supports both per-user and per-machine
installation, whereas it previously supported only per-user installation.
Product A supports only per-user installation, so the upgrade code search
fails if Product B was installed per-machine.

How do I create a check for Product B that will work for the existing
version and future versions as well?

Here is the relevant portion of the log:

MSI (c) (84:D0) [18:56:01:143]: Doing action: FindRelatedProducts
Action 18:56:01: FindRelatedProducts. Searching for related applications
Action start 18:56:01: FindRelatedProducts.
MSI (c) (84:D0) [18:56:01:143]: FindRelatedProducts: current install is
per-user.  Related install for product
'{7124DD21-022E-4868-B9B3-B139C6BD8F77}' is per-machine.  Skipping...
Action ended 18:56:01: FindRelatedProducts. Return value 1.
--
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly 
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users