I have a bundle based on WixStdBa which installs .Net 4.0 and my MSI. I need to add a third party MSI which requires .Net 3.51. So at this point I am only trying to add .Net 3.51 to my chain. Not finding a built-in way to do this like I did for .Net 4.0 ( '<PackageGroupRef Id='NetFx40Web' />') I am using info from:
http://stackoverflow.com/questions/12628922/using-wix3-6-to-install-net-framework-3-5-sp1-with-burn When I added RemotePayload element I get the error message as documented in this thread: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/LGHT0103-Error-td7582776.html " <ExePackage Name='data\dotnetfx35.exe' DownloadUrl='http://www.microsoft.com/en-us/download/confirmation.aspx?id=22' PerMachine='yes' Permanent='yes' Cache='yes' CacheId='dotNetFx3.51'> <RemotePayload CertificatePublicKey="F321408E7C51F8544B98E517D76A8334052E26E8" CertificateThumbprint="D57FAC60F1A8D34877AEB350E83F46F6EFC9E5F1" Description=".NET Framework 3.5 Setup" Hash="3DCE66BAE0DD71284AC7A971BAED07030A186918" ProductName=".NET Framework 3.5" Size="242743296" Version="3.5.30729.1" /> </ExePackage> " Results in: "------ Build started: Project: QDsetup, Configuration: Debug x86 ------ C:\Program Files (x86)\MSBuild\Microsoft\WiX\v3.x\wix2010.targets(971,5): warning : The referenced project '..\WixExt\WixExt\WixExt.csproj' does not exist. C:\Program Files (x86)\WiX Toolset v3.7\bin\candle.exe -dDebug -dDEBUG -d"DevEnvDir=c:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\\" -dSolutionDir=C:\Users\phogland\Documents\Development\Installs\8.7_WIX\QDsetup\ -dSolutionExt=.sln -dSolutionFileName=QDsetup.sln -dSolutionName=QDsetup -dSolutionPath=C:\Users\phogland\Documents\Development\Installs\8.7_WIX\QDsetup\QDsetup.sln -dConfiguration=Debug -dOutDir=bin\Debug\ -dPlatform=x86 -dProjectDir=C:\Users\phogland\Documents\Development\Installs\8.7_WIX\QDsetup\ -dProjectExt=.wixproj -dProjectFileName=QDsetup.wixproj -dProjectName=QDsetup -dProjectPath=C:\Users\phogland\Documents\Development\Installs\8.7_WIX\QDsetup\QDsetup.wixproj -dTargetDir=C:\Users\phogland\Documents\Development\Installs\8.7_WIX\QDsetup\bin\Debug\ -dTargetExt=.exe -dTargetFileName=QDsetup.exe -dTargetName=QDsetup -dTargetPath=C:\Users\phogland\Documents\Development\Installs\8.7_WIX\QDsetup\bin\Debug\QDsetup.exe -out obj\Debug\ -arch x86 -ext ..\WixExt\bin\Release\WixExt.dll -ext "C:\Program Files (x86)\WiX Toolset v3.7\bin\\WixNetFxExtension.dll" -ext "C:\Program Files (x86)\WiX Toolset v3.7\bin\\WixUtilExtension.dll" -ext "C:\Program Files (x86)\WiX Toolset v3.7\bin\\WixTagExtension.dll" -ext "C:\Program Files (x86)\WiX Toolset v3.7\bin\\WixBalExtension.dll" QDsetup.wxs Windows Installer Xml Compiler version 3.7.1224.0 Copyright (C) Outercurve Foundation. All rights reserved. QDsetup.wxs C:\Program Files (x86)\WiX Toolset v3.7\bin\Light.exe -out C:\Users\phogland\Documents\Development\Installs\8.7_WIX\QDsetup\bin\Debug\QDsetup.exe -pdbout C:\Users\phogland\Documents\Development\Installs\8.7_WIX\QDsetup\bin\Debug\QDsetup.wixpdb -ext ..\WixExt\bin\Release\WixExt.dll -ext "C:\Program Files (x86)\WiX Toolset v3.7\bin\\WixNetFxExtension.dll" -ext "C:\Program Files (x86)\WiX Toolset v3.7\bin\\WixUtilExtension.dll" -ext "C:\Program Files (x86)\WiX Toolset v3.7\bin\\WixTagExtension.dll" -ext "C:\Program Files (x86)\WiX Toolset v3.7\bin\\WixBalExtension.dll" -contentsfile obj\Debug\QDsetup.wixproj.BindContentsFileList.txt -outputsfile obj\Debug\QDsetup.wixproj.BindOutputsFileList.txt -builtoutputsfile obj\Debug\QDsetup.wixproj.BindBuiltOutputsFileList.txt -wixprojectfile C:\Users\phogland\Documents\Development\Installs\8.7_WIX\QDsetup\QDsetup.wixproj obj\Debug\QDsetup.wixobj Windows Installer Xml Linker version 3.7.1224.0 Copyright (C) Outercurve Foundation. All rights reserved. light.exe(0,0): error LGHT0103: The system cannot find the file '' with type ''. Done building project "QDsetup.wixproj" -- FAILED. Build FAILED. " As it turns out the Business Management is probably going to insist that I come up with a solution that does not require a Internet connection, so I probably won't be able to use RemotePayload but I was trying to understand the various approaches. If I use the following I get a clean build: " <ExePackage Name='data\dotnetfx35.exe' SourceFile='<path to package>\Microsoft\dotnetframework\DotNet3.5SP1\Full\dotnetfx35.exe' PerMachine='yes' Permanent='yes' Cache='yes' CacheId='dotNetFx3.51' /> " I also checked the Bugs for this RemotePayload issue, raised previously, but did not find it reported. Should it be? Any advise on how to install .Net 3.5 as I expect that running the Microsoft package will not work on Windows 7 or later without also writing some kind of a CA to call DISM. Phill -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/RemotePayload-causes-error-LGHT0103-The-system-cannot-find-the-file-with-type-tp7587545.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
