I thought that was fixed in v3.5.2305.0. Double-check that the wix2010.targets file is correct. You can try setting the MSBuild property RunWixToolsOutOfProc to true as a workaround.
-----Original Message----- From: Yann Normand [mailto:yann.norm...@avanade.com] Sent: Tuesday, November 23, 2010 4:45 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Running HeatDirectory task fails from TFS 2010 with MSBuild x64 ( Wix 3.5.2312) Hi all, I call HeatDirectory task from a MSBuild file. When the MSBuild file is launched from a TFS 2010 Build Server on a x64 system, it fails with the following error: ---------------------------------------------------------------------------- ------------------------------------------------------ F:\Builds\1\MyApplication\CIBuild\Sources\Main\Build\..\Reference\wix\3.5\He at.exe dir F:\Builds\1\MyApplication\CIBuild\Sources\Main\Source\Setup.MyApplicationWeb \..\..\DeployTemp\MyApplication -cg C.MyApplication -dr D.MyApplication -ke -scom -sreg -srd -var var.MyApplication.PublishDir -gg -out F:\Builds\1\MyApplication\CIBuild\Sources\Main\Source\Setup.MyApplicationWeb \MyApplication.generated.wxs Could not load file or assembly 'file:///F:\Builds\1\MyApplication\CIBuild\Sources\Main\Reference\wix\3.5\He at.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, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, 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.ExecuteToolThrea d(Object parameters) ---------------------------------------------------------------------------- ----------------------------------------------------------------- It works if I modify my build to explicitely run MSBuild in x86. Is it a bug in Wix or is there something I missed ? Similar stories I found on the web only confused me. Thanks for anyone who can help me. Yann ---------------------------------------------------------------------------- -- Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
