Yes, they are the same. The MSP just updated files only, no any component
change.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Friday, August 20, 2010 8:00 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] (no subject)
They are the s
Oh, I'm trying to keep it simple here :)
On 10-08-20 4:14 PM, Blair wrote:
> Or, alter your upgrade table to something that allows whatever your SxS
> story is.
>
> -Original Message-
> From: Sohail Somani [mailto:soh...@taggedtype.net]
> Sent: Thursday, August 19, 2010 12:38 PM
> To: wix-
Awesome, thanks. I'm probably going to stick with ComponentGroupRef as
the code generating my installers already works with that :D
On 10-08-20 4:12 PM, Blair wrote:
> Actually, wixlib and ComponentGroup/ComponentGroupRef.
>
> -Original Message-
> From: Blair [mailto:os...@live.com]
> Sen
They are the same between the old and the new merge modules?
-Original Message-
From: Chunlin Liu [mailto:c...@esri.com]
Sent: Friday, August 20, 2010 1:38 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] (no subject)
Yes, they have the exact same Co
Yes, they have the exact same Component Guids. They were included in both setup
through the same mergemodule.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Friday, August 20, 2010 12:39 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users]
Or, alter your upgrade table to something that allows whatever your SxS
story is.
-Original Message-
From: Sohail Somani [mailto:soh...@taggedtype.net]
Sent: Thursday, August 19, 2010 12:38 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] UpgradeGUID question
On 10-08-19 1
Actually, wixlib and ComponentGroup/ComponentGroupRef.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Friday, August 20, 2010 1:12 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: RE: [WiX-users] Shared files/registry question
wixlib
-Original Me
wixlib
-Original Message-
From: Sohail Somani [mailto:soh...@taggedtype.net]
Sent: Thursday, August 19, 2010 1:14 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Shared files/registry question
Hi,
I have 4 products for which I need installers. Each installer requires 3
DLLs
Only via your own UI (either embedded, external (requires a bootstrapper
where you can place your UI), or in your own bootstrapper before starting
the MSI transaction.
You could use IDCRL from a custom action.
-Original Message-
From: Pratapa Reddy Sanaga [mailto:pratap.san...@gmail.com]
Thanks Blair.
On 08/20/2010 03:54 PM, Blair wrote:
> If the new version of the file has the same name as the old file and goes
> into the same directory, keep the component's guid the same.
>
> -Original Message-
> From: Chris Lord [mailto:chris.l...@atterotech.com]
> Sent: Thursday, Augus
If the new version of the file has the same name as the old file and goes
into the same directory, keep the component's guid the same.
-Original Message-
From: Chris Lord [mailto:chris.l...@atterotech.com]
Sent: Thursday, August 19, 2010 9:13 AM
To: General discussion for Windows Installe
Set the SKIPCONFIGUREIIS property to some value when you detect that you are
not installing and haven't already installed any of your features that do
need IIS.
-Original Message-
From: Igor Lemsky [mailto:igor.lem...@gmail.com]
Sent: Thursday, August 19, 2010 3:22 AM
To: General discussi
The shared files should also share the exact same Component Guids and
component composition (what is inside of each component).
-Original Message-
From: Chunlin Liu [mailto:c...@esri.com]
Sent: Friday, August 20, 2010 10:47 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] (no s
It's because it's an advertised shortcut that has the intentional effect of
doing resiliency check on the feature the target component belongs to. I think
there's an advertised attribute for shortcuts you can set to "no", IIRC.
Phil Wilson
-Original Message-
From: MYFLEX [mailto:shrin
Hi,
I has two product MSI setups, A.msi and B.msi. They have some shared files
installed to "Program Files\Common Files". I need update some of them in our
Service Pack. I created A_sp1.msp and B_sp1.msp to update those shared files.
I have A and B installed on one machine. I also applied A_sp1
Hi,
I has two product MSI setups, A.msi and B.msi. They have some shared files
installed to "Program Files\Common Files". I need update some of them in our
Service Pack. I created A_sp1.msp and B_sp1.msp to update those shared files.
I have A and B installed on one machine. I also applied A_sp1
Hi All,
I've just followed this example
http://wix.sourceforge.net/manual-wix3/create_start_menu_shortcut.htm to the
letter in my own script but still no short cut. Do I need to be doing
something else for this to work on Windows 7?
Thanks,
James
LalPac Limited registered in England
Set the PreprocessorVariable. It's an optional string parameter that will
substitute SourceDir for another variable name (ex: var.Dir).
-Original Message-
From: Satyaprakash J [mailto:sat...@smartek21.com]
Sent: Friday, August 20, 2010 2:54 AM
To: wix-users@lists.sourceforge.net
Subject:
This is something I've been meaning to tackle as I make extensive ( and I mean
really extensive ) use of Product Configurations and Release Flags in
InsallShield. Basically with WiX you have to break everything out into
fragments and then instead of using release flags you use FeatureRef and
Hi All,
I have a couple of questions regarding WIX. How can I have multiple
releases(like in Installshield) with one project? Also is it possible to
specify any property like PRODUCTCODE during building the project?
Thanks,
Akshi
--
View this message in context:
http://windows-installer-xml-w
Hi
I run the following command to generate the attached .wxs file.
heat dir
"\\192.168.10.61\Share\WebAppBuildDef\WebAppBuildDef_20100808.2\Debug"
-gg -sfrag -sreg -template:product -out directory.wxs -cg WebAppComponentGroup
In the directory.wxs file the Source attribute of
21 matches
Mail list logo
