Re: [WiX-users] [WIX]: How to extract the files in selected folder using MSI dialog.

Please find the log files attached here On Fri, Mar 27, 2015 at 12:31 AM, Nir Bar wrote: > Can you upload the log file? > > > > - > Nir Bar > Freelance Developer > Mail: nir@panel-sw.com > Web: www.panel-sw.com >- C++ On Windows, Linux and Embedded Platforms >- WiX & InstallShiel

Re: [WiX-users] Predicting Bootstrapper Cache Location

Phill's comment was incorrect, the provider key will be generated for you automatically if you don't specify it. This behavior is a bug that I'm currently working on: http://wixtoolset.org/issues/4630/ On Thu, Mar 26, 2015 at 7:06 PM, Edwin Castro wrote: > The remarks at > > http://wixtoolset.o

Re: [WiX-users] Predicting Bootstrapper Cache Location

The remarks at http://wixtoolset.org/documentation/manual/v3/xsd/dependency/providerkey.html say This provider key is designed to persist throughout compatible upgrades so that dependent bundles do not have to be reinstalled and *will not prevent your product from being upgraded*. If this attribut

Re: [WiX-users] Predicting Bootstrapper Cache Location

>>So it looks like the bootstrapper is not passing BUNDLEPROVIDERKEY to the MSI at all. You need to define Bundle/@ProviderKey, here . I set it to a GUID (and like UpgradeCode I do not change the Bundle/@ProviderKey between b

Re: [WiX-users] Predicting Bootstrapper Cache Location

This post may help: http://stackoverflow.com/questions/17269942/not-possible-to-pass-wixbundleproviderkey-variable-to-msipackage - Nir Bar Freelance Developer Mail: nir@panel-sw.com Web: www.panel-sw.com - C++ On Windows, Linux and Embedded Platforms - WiX & InstallShield --

Re: [WiX-users] WIX force GUI on uninstall

You can do that with burn as a bootstrapper. - Nir Bar Freelance Developer Mail: nir@panel-sw.com Web: www.panel-sw.com - C++ On Windows, Linux and Embedded Platforms - WiX & InstallShield -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.na

Re: [WiX-users] [WIX]: How to extract the files in selected folder using MSI dialog.

Can you upload the log file? - Nir Bar Freelance Developer Mail: nir@panel-sw.com Web: www.panel-sw.com - C++ On Windows, Linux and Embedded Platforms - WiX & InstallShield -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WIX-How

Re: [WiX-users] Predicting Bootstrapper Cache Location

I had not defined BUNDLEPROVIDERKEY in my MSI *but* I was just trying to verify that the data was passed from the bootstrapper to the MSI by checking the bootstrapper and MSI logs. In the bootstrapper log I see [0BE4:13F4][2015-03-26T11:43:52]i301: Applying execute package: projectName.msi, actio

Re: [WiX-users] Predicting Bootstrapper Cache Location

Did you define the property in you MSI and declare it as Secure? Ex (with remember-me pattern in place): ... ... CMDLINE_BUNDLEPROVIDERKEY -Original Message- From: Edwin Castro [mailto:egca...@gmail.com] Sent: Thursday, March 26, 2015 11:51 AM To:

Re: [WiX-users] Predicting Bootstrapper Cache Location

Jacob, You mentioned something interesting that I can't get to work. I tried But BUNDLEPROVIDERKEY is always empty in the msi log. Should I expect that to work? -- Edwin G. Castro On Thu, Mar 26, 2015 at 7:52 AM, Hoover, Jacob wrote: > To extend upon Phil's suggestion, > http

Re: [WiX-users] Keep Desktop Shortcuts and Pinned Task Bar Icons with Upgrades

If you just leave them alone WiX should generate stable GUID's for you assuming you don't rename them/change the paths( see -ag). I would not advise using heat for anything other than an initial generation of the WXS file. -Original Message- From: Tobias Markmann [mailto:tmarkm...@google

Re: [WiX-users] Keep Desktop Shortcuts and Pinned Task Bar Icons with Upgrades

Hi Phil, On Thu, Mar 26, 2015 at 4:22 PM, Phil Wilson wrote: > An early sequencing of the upgrade (such as after InstallIntialize) is > more or less the same as uninstalling the old product then installing > the new one. Guids don't really matter much. > > After InstallExecute isn't like that. A

[WiX-users] wix bundle installation

Hello! My problem: When I execute my bundle installer.exe, which fits several msi packages (applications & drivers), a second installer dialog is opened additionally at the end of the installation (First installation dialog is still open). This only happens on Windows 7 x86 systems and not on x

Re: [WiX-users] Keep Desktop Shortcuts and Pinned Task Bar Icons with Upgrades

An early sequencing of the upgrade (such as after InstallIntialize) is more or less the same as uninstalling the old product then installing the new one. Guids don't really matter much. After InstallExecute isn't like that. As an example: say every file has a guid and a version or hash. The guid i

Re: [WiX-users] Predicting Bootstrapper Cache Location

To extend upon Phil's suggestion, http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Updater-application-using-Bootstrapper-UI-Bundle-td7596579.html -Original Message- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: Thursday, March 26, 2015 7:11 AM To: wix-users@list

Re: [WiX-users] Keep Desktop Shortcuts and Pinned Task Bar Icons with Upgrades

Sounds like you broke component rules somewhere... Are your component ID's identical for the same files across MSI's? Are you using version info on the files in question, or is it falling back to timestamp and hash checking? -Original Message- From: Tobias Markmann [mailto:tmarkm...@g

Re: [WiX-users] [WIX]: Execute setup.exe from MSI package location (which is not packaged) using MSI.

Use burn... Calling one installer from another installer is not supported. https://msdn.microsoft.com/en-us/library/aa368010(v=vs.85).aspx -Original Message- From: Dileep S [mailto:dileep.sanamp...@gmail.com] Sent: Thursday, March 26, 2015 12:12 AM To: General discussion for Windows Ins

Re: [WiX-users] Keep Desktop Shortcuts and Pinned Task Bar Icons with Upgrades

Hi Rob, On Thu, Mar 26, 2015 at 12:27 AM, Rob Mensching wrote: > Schedule your upgrade late and carefully adhere to the Component Rules. > Thanks for the hint. I googled a bit and read up things on MajorUpgrade scheduling [0] and Component Rules, including [1] and [2]. So I've tried scheduling

Re: [WiX-users] Predicting Bootstrapper Cache Location

I described one approach in this thread . -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Predicti

Re: [WiX-users] 'INSERT INTO' an offline MSI with DTF

For anyone who may be interested, using the DTF module with Powershell (external to an MSI) requires code in the following format: # PowerShell - # Add Required Type Libraries Add-Type -Path "C:\Program Files (x86)\WiX Toolset v4.0\bin\WixToolset.Dtf.WindowsInstaller.dll"; # Open an MSI

[WiX-users] WIX force GUI on uninstall

Hello, I am using wix(3.8) to create an installer for a WPF application developed in VS 2012.I have created some special dialogue that need to be displayed when uninstall.This works ok if the user uses original msi to uninstall (double click on msi and the maintenance dialog appears).When us