Re: [WiX-users] Conditionally Installing Update MSI's in Burn

Hi Jacob, I couldn't understand your " Thanks.. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Conditionally-Installing-Update-MSI-s-in-Burn-tp7581445p7581472.html Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] What is the purpose of the auto start that is created

Hi there, Burn 3.6 seems to be triggering MS Forefront popup warnings during installation / uninstallation, due to RunOnce registry Keys being amended There have been a couple of threads on this issue, and none have a resolution. One... ( What-is-the-purpose-of-the-auto-start-that-is-created <

[WiX-users] Burn 3.6 (or Wix ExtBA) causing MS Forefront Warnings due to RunOnce registry Keys

Hi there, Burn 3.6 seems to be triggering MS Forefront popup warnings during installation / uninstallation, due to RunOnce registry Keys being amended. Needless to say I'm not specifically doing anything with the RunOnce keys. The only potential non-standard thing I'm doing with burn is using Ne

Re: [WiX-users] How to create and reference a custom pre-requisite package

Hi Raj, thanks for your response. I can put all the third party components in their own MSI (in fact I have now done just that) but since the MSI is currently within the Bootstrapper.exe its self it will always get downloaded with each update. *How* do I set this "thirdpartycomponents.msi" up to

Re: [WiX-users] How to create and reference a custom pre-requisite package

OK thanks, I think I'm getting there So, I have my MsiPackage for my download... https://mycompany.com/downloads/blahblah/sharedcomponents.msi"; DisplayName="Shared Components" Compressed="no" Vital="yes"> One piece of missing info I cannot find in the docume

Re: [WiX-users] How to create and reference a custom pre-requisite package

Thanks Neil, I knew security would be an issue / can of worms, but at least I can now stop looking for something that doesn't exist :) Cheers again. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-create-and-reference-a-custom-pre-requisite

Re: [WiX-users] How to create and reference a custom pre-requisitepackage

Thanks Dave. Luckily for us the items we want to store can reside in an unsecured folder, so I don't need to jump through that hoop. I'm getting failed installs due to hash match failures, but in the scheme of things its probably best I create another topic. Thanks for your feedback :) -- View

Re: [WiX-users] How to create and reference a custom pre-requisitepackage

I've changed my mind re separate question :) Unless I'm understanding this incorrectly so long as it does not change, the sharedcomponents.msi (which holds a number of third party dll's that will not change) only needs to be in one place (i.e. the DownloadURL in the MsiPackage element will not cha

Re: [WiX-users] How to create and reference a custom pre-requisitepackage

Thanks Rob, Yep, my MSI isn't changing. I don't seem to be able to determine why it thinks the hash doesn't match. If build 153 created the MSI, and builds 153, 154, 155 etc are looking at the same DownLoadURL location (and presumably the same target hash values), why do Bootstrappers 154 and 155

Re: [WiX-users] How to create and reference a custom pre-requisitepackage

OK. I should have known - rob was right all along (smile) *Assuming* that WiX generates it's hash values the same way as the ms "File Checksum Integrity Verifier" (http://download.microsoft.com/download/c/f/4/cf454ae0-a4bb-4123-8333-a1b6737712f7/windows-kb841290-x86-enu.exe) then the hash values o

Re: [WiX-users] How to create and reference a custom pre-requisitepackage

I think I've been having a few blonde moments. (sigh) My build is re-creating this "static" msi file each build, so that the file date is changing. If I just build the thing and include the file as a static resource instead then it *will* be the same hash value. I need to get out more... -- Vi

Re: [WiX-users] Error 2902: Operation ixfAssemblyCopy called out of sequence.

Hi Rob, I thought that was what you meant re InstallExecuteSequence :) Phil the sizes were nothing to worry about so that wasn't it. In the end it looks like it was down to re-used Component ID or File ID's. I noticed that these were the same as in another package, and out of sheer desperation cha

[WiX-users] Leave components installed between upgrades -but not permanent?

We're using burn to create a bootstrapper app that then loads a number of applications within their own MSI's. All of these applications have some third party shared components (ms libraries, DevX controls etc) that are installed in the GAC and will not change *very often* as they are outside of o

Re: [WiX-users] Leave components installed between upgrades -but not permanent?

Thanks for the reply (Schedule major upgrade late and ensure Component Rules are followed. ) Rob. I'm not sure I follow. Hopefully I'm following the component rules as all resources used more than once are only installed via one MSI in the GAC - lets call it SharedComponents.msi. In my (simplifi

Re: [WiX-users] Burn not show installed prerequisites (LocalDB) MSI in Program and Features

If I understand your situation correctly, the MsiPackage element in your chain should have a Visible property. simply set this to "yes". >From the docs: Specifies whether the MSI will be displayed in Programs and Features (also known as Add/Remove Programs). If "yes" is specified the MSI package i

Re: [WiX-users] Antivirus is blocking execution of standard bootstrapper application

Which AV software is doing this? We're currently not signing, so by the sounds of things may be lucky to have not come across this. Knowing which AV has this behaviour would be very handy. Thanks -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Ant