In your question, where are you trying to do something incomprehensible, it is unclear, so I will start from the very beginning.
Create a new Wix Burn download project. Your dependencies will be installed here, and then your existing Wix 3.5 installer will be created.
Download the complete .net 3.5 SP1 package and note the direct URL used to download it.
Using heat.exe (in the wix 3.6 bin directory), run the following command, which will generate a WXS file with the details of the .net installer.
heat.exe payload [path_to_net_installer] -o [path_to_wxs]
this.will will give you the following in wxs:
<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" />
Add this to the bootstrapper project as a child of ExePackage and update the element with the previously saved download URL. This will download the .net installer automatically, or you can place it next to the boot exe file and it will detect it.
Create a chain in the Bundle that contains .net ExePackage and MsiPackage for your installer. Then you will get something like (many necessary attributes, I will leave you to fill!):
<Bundle Name="$(var.SkuName)" Copyright="$(var.Copyright)" Manufacturer="$(var.Manufacturer)" Version="$(var.ProductVersion)" UpgradeCode="$(var.UpgradeCode)"> <Chain> <ExePackage Id="dotNetFX3.5"> <RemotePayload /> </ExePackage> <MsiPackage Id="MyMsi" /> </Chain> </Bundle>
The assembly, and then you should have a large exe with msi enabled, or if you decide not to compress it with the exe that your msi runs (it should be in the same folder).
caveman_dick
source share