WiX v2 did not run the static analysis tools (ICE). WiX v3 we started
running the tools automatically to help everyone find bugs before they
shipped.
On Wed, Jun 20, 2012 at 2:13 AM, Gareth wrote:
> Hi Rob,
>
> Thanks for your attention, I did as requested, but was not getting the same
> result -
Hi Rob,
Thanks for your attention, I did as requested, but was not getting the same
result - I am now getting a more useful and expected error message of
"LGHT0345 : '...\Microsoft_VC100_CRT_x64.msm' is a 64-bit merge module but
the product consuming it is 32-bit. 32-bit products can consume only
On 13-Jun-12 06:22, Gareth wrote:
> Yes it can.
You can also use a hammer to tighten a screw, but it's not recommended.
The VC9 and VC10 CRTs are very different (VC9 goes into the Fusion GAC;
VC10 doesn't) so it's no surprise they behave differently.
--
sig://boB
http://joyofsetup.com/
---
Most likely the VC100 Merge Module changed and no longer support doing what
was done in VC90. We didn't purposely change the WiX toolset to block it.
If you run with the -notidy switch to light (I think that's the name) there
should be a log file somewhere under %TEMP% that will show the mergemod.
Bob Arnson-6 wrote
>
>> then how can a 64-bit operating system interogate a bespoke file format
>> in
>> order to draw a thumbnail preview when it is installed as part of a
>> 32-bit
>> package?
> It can't. That requires a 64-bit package, as I said. The rules are that
> a 32-bit package can cont
] light.exe error when merging VC100 merge modules for
both x86 and x64
On 18-May-12 11:32, Gareth wrote:
> But you can install 64-bit dlls withoin a 32-bit package - they're just
> files.
Not if they're marked as a 64-bit component that goes into a 64-bit part
of the file system. Then
On 18-May-12 11:32, Gareth wrote:
> But you can install 64-bit dlls withoin a 32-bit package - they're just
> files.
Not if they're marked as a 64-bit component that goes into a 64-bit part
of the file system. Then they're "special."
> then how can a 64-bit operating system interogate a bespoke f
@serif.com]
Sent: May-18-12 11:32 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] light.exe error when merging VC100 merge modules for
both x86 and x64
But you can install 64-bit dlls withoin a 32-bit package - they're just
files. So, we add a dll that allows the 64-bit oper
But you can install 64-bit dlls withoin a 32-bit package - they're just
files. So, we add a dll that allows the 64-bit operating system to
interogate our bespoke document formats in order to draw pretty thumbnail
previews. But this code only works if the operating sytem has the required
dependencie
On 11-May-12 04:53, Gareth wrote:
> Hi Bob, thanks for your input, but why would it ever be necessary to include
> 32-bit merge modules in a 64-bit package?
When you have a 64-bit component like a shell extension but everything
else is 32-bit. MSI doesn't support a 32-bit package with 64-bit compo
Hi Bob, thanks for your input, but why would it ever be necessary to include
32-bit merge modules in a 64-bit package? You can't install a 64-bit
package on a 32-bit operating system, so they'd never be used.
The otherway around though - you can install a 32-bit package on a 64-bit
operating syst
On 08-May-12 11:45, Gareth wrote:
> Up until now I have been able to merge VC90 merge modules of both x86 and x64
> varieties into the same package without any problem.
That's legal in an x64 package only.
--
sig://boB
http://joyofsetup.com/
-
Up until now I have been able to merge VC90 merge modules of both x86 and x64
varieties into the same package without any problem. Now that we've moved on
to Visual Studio 2010 for our applications, I must similarly update my merge
module inclusions. If I attempt to merge just the x86 versions, I g
13 matches
Mail list logo
