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
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
I described one approach in this thread
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-Burn-managing-installed-products-after-initial-install-td7595346.html#a7595368
.
--
View this message in context:
Hi Rob,
On Thu, Mar 26, 2015 at 12:27 AM, Rob Mensching r...@firegiant.com 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
Please find the log files attached here
On Fri, Mar 27, 2015 at 12:31 AM, Nir Bar nir@panel-sw.com 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
Jacob,
You mentioned something interesting that I can't get to work. I tried
Chain
MsiPackage SourceFile=$(var.projectName.TargetPath)
MsiProperty Name=BUNDLEPROVIDERKEY Value=[WixBundleProviderKey]/
/MsiPackage
/Chain
But BUNDLEPROVIDERKEY is always empty in the msi log.
Should I
Did you define the property in you MSI and declare it as Secure?
Ex (with remember-me pattern in place):
Property Id=BUNDLEPROVIDERKEY Secure=yes
RegistrySearch Id=FindBundleProviderKey Root=HKLM
Key=SOFTWARE\$(var.ApplicationKeyPath) Name=BundleProviderKey Type=raw /
/Property
Hi Phil,
On Thu, Mar 26, 2015 at 4:22 PM, Phil Wilson phildgwil...@gmail.com 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
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
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:
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:
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,
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
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 egca...@gmail.com wrote:
The remarks at
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
--
So it looks like the bootstrapper is not passing BUNDLEPROVIDERKEY to the
MSI at all.
You need to define Bundle/@ProviderKey, here
http://wixtoolset.org/documentation/manual/v3/xsd/wix/bundle.html . I
set it to a GUID (and like UpgradeCode I do not change the
Bundle/@ProviderKey between
No, its not uninstallable. Looks like I'm done for :) Thanks for your help
anyway.
On Thu, Mar 26, 2015 at 2:43 AM, Nir Bar nir@panel-sw.com wrote:
Is the v1.0.2 patch uninstallable
https://msdn.microsoft.com/en-us/library/aa372102(v=vs.85).aspx ?
If yes you can uninstall it in v1.0.3
Hi All,
I have created MSI using WIX with InstallDir dialogs.
I have extracted the MSI package with default. While extracting it shows
UAC prompt and then extracted successfully.
But, second time installation, i have changed the folder to extract.
This time, it was not showing any UAC prompt
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:
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
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
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
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
23 matches
Mail list logo
