That error is the Generic Error for trying to build a 64 bit item on a  
32 bit installation.

Your configuration is either:
1. 64 Bit Wix Tools on a 32-bit TFS Install
2. 32 bit Heat.exe trying to gather 64 bit binaries.

I believe John is going to tell you to change the MSBuild Target to "x86"

Quoting John Cooper <jocoo...@jackhenry.com>:

> On your build definition, what is your setting for "MSBuild Platform"?
>
> --
> John Merryweather Cooper
> Senior Software Engineer | Enterprise Service Applications |  
> Continuing Development
> Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext:  431050  
> |jocoo...@jackhenry.com
>
>
>
> -----Original Message-----
> From: Farrukhw [mailto:farru...@gmail.com]
> Sent: Wednesday, September 24, 2014 8:28 AM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] HeatDirectory failure on TFS
>
> Hi experts,
> I'm using HeatDirectory task in my *.wixproj file, which is working  
> very fine on my machine, being built locally.
>
> However, on TFS, it is failing with following error:
>
> C:\Program Files (x86)\WiX Toolset v3.8\bin\Heat.exe dir  
> D:\Builds\32\48\bin\Debug\InstallSrc\WebApp\ -cg CompGrp_WebApp -dr  
> WebApp -ke -scom -sreg -srd -var var.WebAppSrc -v -ag -sfrag -suid  
> -out WebApp_.wxs
>          Could not load file or assembly 'file:///C:\Program Files  
> (x86)\WiX Toolset v3.8\bin\Heat.exe' or one of its dependencies. An  
> attempt was made to load a program with an incorrect format.
>             at System.Reflection.RuntimeAssembly._nLoad(AssemblyName
> fileName, String codeBase, Evidence assemblySecurity,  
> RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr  
> pPrivHostBinder, Boolean throwOnFileNotFound, Boolean  
> forIntrospection, Boolean
> suppressSecurityChecks)
>             at
> System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName
> assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly,  
> StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean  
> throwOnFileNotFound, Boolean forIntrospection, Boolean
> suppressSecurityChecks)
>             at
> System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName
> assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly,  
> StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean  
> forIntrospection, Boolean suppressSecurityChecks)
>             at System.Reflection.RuntimeAssembly.InternalLoadFrom(String
> assemblyFile, Evidence securityEvidence, Byte[] hashValue,  
> AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection,  
> Boolean suppressSecurityChecks, StackCrawlMark& stackMark)
>             at System.Reflection.Assembly.LoadFrom(String assemblyFile)
>             at
> Microsoft.Tools.WindowsInstallerXml.Build.Tasks.WixToolTask.ExecuteToolThread(Object
> parameters)
>      0>MSBUILD : error MSB4166: Child node "3" exited prematurely.  
> Shutting down. Diagnostic information may be found in files in the  
> temporary files directory named MSBuild_*.failure.txt.
>
>
> However, on same build machine, I tried to execute heat command line  
> (generated by above log) and got it working fine: i.e.
> C:\Program Files (x86)\WiX Toolset v3.8\bin\Heat.exe dir  
> D:\Builds\32\48\bin\Debug\InstallSrc\WebApp\ -cg CompGrp_WebApp -dr  
> WebApp -ke -scom -sreg -srd -var var.WebAppSrc -v -ag -sfrag -suid  
> -out WebApp_.wxs
>
>
>
> I even tried it, by disabling MsBuild Multi-Proc (building projects in
> parallel) in TFS definition, but in vain.
>
> Why it is failing on TFS, but not locally?
>
> Thanks a bunch.....
>
>
>
>
>
> --
> View this message in context:  
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/HeatDirectory-failure-on-TFS-tp7596956.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer  
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS  
> Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download  
> White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with  
> EventLog Analyzer  
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&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.
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>




------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&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