Use the Name attribute.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: manmaor [mailto:manma...@gmail.com]
Sent: Sunday, January 18, 2015 12:38 PM
To: wix-users@lists.sour
On 18-Jan-15 15:37, Phill Hogland wrote:
> I have noticed, in several different bundles and rollback situations, that if
> a Bundle/@Chain contains a RollbackBoundry, and when a msi package fails
> during install, right after the RollbackBoundry, that at least sometimes,
> the Bundle is left in a s
no, when I said :
>> but it require the msi installer to be near the bootstrapper.exe.
I meant the installer.msi needed to be in the same directory with the
bootstrapper.exe to be installed by the bootstrapper.exe otherwise it wont
be installed.
but what I need is more like adding the installer.m
I have noticed, in several different bundles and rollback situations, that if
a Bundle/@Chain contains a RollbackBoundry, and when a msi package fails
during install, right after the RollbackBoundry, that at least sometimes,
the Bundle is left in a state where it cannot be uninstalled. Also when a
>> but it require the msi installer to be near the bootstrapper.exe.
I'm not sure what you mean. In the MsiPackage I use the following, (with a
bindpath defined in the wixproj):
Compressed='no'
DownloadUrl='{2}'
SourceFile='de-DE\Project.msi'
Name=BundleOutputSubFolderPath\Projec
hello is there an option to install a msi file from a payload ?
I tried to set the compressed property to no but it require the msi
installer to be near the bootstrapper.exe.
If it's not possible, there is any way to set the path of the MsiPackahe to
the assembly path ?
---
6 matches
Mail list logo
