The Platform should be overridden if you pass it as a property on the command 
line.  There are several places (especially dependent on how may configs and 
platforms might have been supported in the past) where defaults are set in a 
*proj file.  You need to make sure that none of the defaults are to "Any CPU" 
unless that is your intent.

Also, it is quite correct that C++ projects require win32 generally.

Note that .NET assemblies are generally built "Any CPU" and installers are 
generally build "x86" or "x64".  This means that the overall solution is 
generally built "Mixed Platform" to get everything building in one pass.

As far as the assembly conflicts warning, this generally occurs when you are 
both building the assembly and using it in other portions of your project via a 
reference to a checked in binary.  Is this the case?  You can also get this 
when different .NET Platform levels are used for different assemblies.

Without seeing the whole mess, it is difficult to know for sure.

--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.®
Shawnee Mission, KS  66227
Office:  913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com



-----Original Message-----
From: Alan Hartmann [mailto:a...@proteledata.com] 
Sent: Thursday, February 13, 2014 2:22 PM
To: 'General discussion about the WiX toolset.'
Subject: Re: [WiX-users] Requesting assistance with two build errors

John:

Ran msbuild and basically got the same error messages.   But in addition I
noticed a warning:

" CrystalDecisions.Windows.Forms, Version=13.0.2000.0, Culture=neutral, 
PublicKeyToken=692fbea5521e1304, processorArchitecture=MSIL 
c:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1605,
5): warning MSB3247: Found conflicts between different versions of the same 
dependent assembly. [c:\projects\econngui\IPPBX_Sys_UI\IPPBX_Sys_UI.csproj]"

I'm not sure if that's related to the problem or not.



-----Original Message-----
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Thursday, February 13, 2014 2:18 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Requesting assistance with two build errors

Well, then, what happens when you build the solution using (from a VS command 
prompt)

Msbuild "path to solution.sln" /p:Platform=x86

--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.®
Shawnee Mission, KS  66227
Office:  913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com





------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.


------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to