To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Visual C++ 2010 Merge Module
That is what the Common Program Files directory was created for
smile/.
You use it similarly to the non-Common directory, except that components
shared between simultaneously installed
: LibBindFiles or BindFiles.
Blair
-Original Message-
From: Joost van Zoest [mailto:jzo...@siqura.com]
Sent: Thursday, February 02, 2012 12:53 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Visual C++ 2010 Merge Module
Hi Blair,
Thank you very much
, 2012 4:38 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Visual C++ 2010 Merge Module
Several action don't seem to be intended to be found in MSMs. Maybe
AppSearch is one of them.
Do you distribute your MSM publically? If not, I've got a couple of
ideas
to force the AppSearch from an MSM.
Blair
-Original Message-
From: Joost van Zoest [mailto:jzo...@siqura.com]
Sent: Wednesday, February 01, 2012 5:11 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Visual C++ 2010 Merge Module
Hi Blair,
Thanks for your
.'
Subject: Re: [WiX-users] Visual C++ 2010 Merge Module
The only reason I asked is because the guid that suffixes the property
names is supposed to be the MSM's Package @Id, and there should be no
reason that your MSM is using another MSMs properties. However, that
appears to be a red herring
.
Subject: Re: [WiX-users] Visual C++ 2010 Merge Module
I've validated my MSM in Orca. At first, I got a lot of ICE33 warnings
because of some COM registration logic. To rule out that this was causing my
problems, I removed this registration logic and validated the MSM again. Now
the validation
Did you borrow VC's MSM's package guid for your MSM?
-Original Message-
From: Joost van Zoest [mailto:jzo...@siqura.com]
Sent: Sunday, January 29, 2012 11:35 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Visual C++ 2010 Merge Module
On 27-Jan-12
...@live.com]
Sent: Monday, January 30, 2012 9:07 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Visual C++ 2010 Merge Module
Did you borrow VC's MSM's package guid for your MSM?
This message contains confidential information and is intended only
pass validation by itself?
Blair
-Original Message-
From: Joost van Zoest [mailto:jzo...@siqura.com]
Sent: Monday, January 30, 2012 12:58 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Visual C++ 2010 Merge Module
If you mean if I've used guids
On 27-Jan-12 17:28, Bob Arnson wrote:
I have made an installer in WIX which embeds 2 merge modules: the
Microsoft_VC100_CRT_x86.msm merge module, and my own module (let's
call this one MyMergeModule.msm for now). When I embed the VC merge
module before MyMergeModule, I get a lot of
I have made an installer in WIX which embeds 2 merge modules: the
Microsoft_VC100_CRT_x86.msm merge module, and my own module (let's call
this one MyMergeModule.msm for now). When I embed the VC merge module
before MyMergeModule, I get a lot of warnings that some actions can not
be merged from
C++ 2010 Merge Module
I have made an installer in WIX which embeds 2 merge modules: the
Microsoft_VC100_CRT_x86.msm merge module, and my own module (let's call this
one MyMergeModule.msm for now). When I embed the VC merge module before
MyMergeModule, I get a lot of warnings that some actions
On 27-Jan-12 04:14, Joost van Zoest wrote:
I have made an installer in WIX which embeds 2 merge modules: the
Microsoft_VC100_CRT_x86.msm merge module, and my own module (let's call
this one MyMergeModule.msm for now). When I embed the VC merge module
before MyMergeModule, I get a lot of
On 27/01/2012 15:59, John Bergman wrote:
Where did you get the merge module for the VC 10.0 Runtime? I have been
looking for one for quite some time.
If you have Visual Studio 2010 installed, it's in C:\Program Files
(x86)\Common Files\Merge Modules
--
Bruce Cran
14 matches
Mail list logo
