Re: [WiX-users] using a variable for Component Win64 attribute value still generating generic warning not uniquely suppressible in wixproj | build | suppress specific warnings field

2010-06-17 Thread Elfe Xu
Hi Bob, I have the same problem and found this very old post. Would you please give me more detail on how to have the compiler supply the default value for the Win64 attribute when the InstallerPlatform .wixproj property is x64 or ia64/intel64 ? Thanks! -Elfe -- View this message in

Re: [WiX-users] using a variable for Component Win64 attribute value still generating generic warning not uniquely suppressible in wixproj | build | suppress specific warnings field

2010-06-17 Thread Blair
From the Candle Task page in the documentation: InstallerPlatform Optional string parameter. Specifies the processor architecture for the package. Valid values are x86, x64, and ia64. (Deprecated values include intel for x86 and intel64 for ia64.) This is equivalent to the -arch switch in

Re: [WiX-users] using a variable for Component Win64 attribute value still generating generic warning not uniquely suppressible in wixproj | build | suppress specific warnings field

2010-06-17 Thread Elfe Xu
Yeah, set the INSTALLPLATFORM property works. I had thought the build platform set by configuration means the INSTALLPLATFORM. It's interesting that if I didn't set this property, the sys.BUILDARCH is still correct (as I'm using Debug | x64), but the win64 is no. Is there any reason that: (1)

Re: [WiX-users] using a variable for Component Win64 attribute value still generating generic warning not uniquely suppressible in wixproj | build | suppress specific warnings field

2010-06-17 Thread Blair
(1) It is common in many big shops that the build platform is standardized servers which may have little to do with the actual target platform of the product. Thus, there is often a need to be explicit. (2) There are many 64-bit packages that install just one 64-bit component and all the rest of

Re: [WiX-users] using a variable for Component Win64 attribute value still generating generic warning not uniquely suppressible in wixproj | build | suppress specific warnings field

2008-11-19 Thread Robert O'Brien
So basically I no longer need to include the Win64 attribute except in cases where the value for a specific component has to be a specific value regardless of what the Platform setting is? -Original Message- From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2008

Re: [WiX-users] using a variable for Component Win64 attribute value still generating generic warning not uniquely suppressible in wixproj | build | suppress specific warnings field

2008-11-19 Thread Bob Arnson
Robert O'Brien wrote: So basically I no longer need to include the Win64 attribute except in cases where the value for a specific component has to be a specific value regardless of what the Platform setting is? Yes, but it's only valid when you need to specify a 32-bit component in a

[WiX-users] using a variable for Component Win64 attribute value still generating generic warning not uniquely suppressible in wixproj | build | suppress specific warnings field

2008-11-18 Thread Robert O'Brien
Background -- A while ago I raised an issue to do with a warning being generated when using a variable for the Component Win64 attribute value. Below you'll see the an excerpt of the logic I'm using so that in the case of all managed code deliverables I can create one set of wix

Re: [WiX-users] using a variable for Component Win64 attribute value still generating generic warning not uniquely suppressible in wixproj | build | suppress specific warnings field

2008-11-18 Thread Bob Arnson
Robert O'Brien wrote: Any insights on how I might still use a $(var.Platform) derived value for the Win64 attribute and also suppress the generic warning generated by every instance where I do this so that my project build doesn't break building when the treat warnings as errors quality