Re: [WiX-users] MSI runs an EXE and it cannot write to a file in programdata folder in windows 8

yes, it didn't help... -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/MSI-runs-an-EXE-and-it-cannot-write-to-a-file-in-programdata-folder-in-windows-8-tp7595915p7595992.html Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Using external cabs

Thanks! I'm good at making things harder than necessary -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-external-cabs-tp7595978p7595983.html Sent from the wix-users mailing list archive at Nabble.com. --

Re: [WiX-users] Using external cabs

On 19-Jul-14 13:09, Phill Hogland wrote: > So when this MSI is added to a bundle, I assume that Payload element should > be used with the MsiPackage element to specify the MSI and the cabinet > files. No need. WiX automatically "harvests" the external cabinets and loose files from an MsiPackage at

[WiX-users] Using external cabs

On a different question (than my other post about signing external ab files), when using the MediaTemplate element in an MSI I understand that it will do 'smart cabbing' and create multiple cab files using the CabinetTemplate (or default) as needed. So when this MSI is added to a bundle, I assume

[WiX-users] wix39 signing external cabs

Until now I have always used the MediaTemplate EmbedCab='yes". My projects in general are posted to a web site and I use a mba to update the bundle and download the packages. This has been working for many projects using wix 3.8.1128. However I have recently experimented with creating these same