Hello,
is there any documentation available on authoring and handling product
dependencies? So far (3.9R2), the "How To: Author product dependencies" in the
WiX help file is sill empty.
I have learnt that Burn can now handle dependencies without using the
Dependency Extension, but I assume that
Hello,
we are migrating from another chained MSI installation (in fact we used
ISChainer, but I do not think that matters) to Burn.
There are several bundles that may be installed in parallel and that share some
of their packages. With WiX 3.9R2, the dependencies among these Burn bundles
are t
://msdn.microsoft.com/en-us/library/aa370579(v=vs.85).aspx
Steve
-Original Message-
From: Reuss, Matthias [mailto:matthias.mr.re...@sivantos.com]
Sent: June-26-15 8:34 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Does Burn allow minor upgrades of packages?
Hello,
Does Burn
Hello,
Does Burn allow minor upgrades of MsiPackages? Are there some attributes that
can be set to achieve that? Or do I have to write custom code that makes the
bootstrapper think that the package to be upgraded is not yet there?
Best regards
Matthias Reuss
-
Hello,
Is there a built-in way for an MSI package to detect that it was started from a
Bundle?
(E.g. a property that Burn automatically sets)
We are going to set such a property using an MSIProperty element, but if that
feature is already built-in, we don't need to do it ourselves.
Best regar
Hi Ronny,
In your log file, action InstallValidate, you get a list of all the components
and whether or not they are installed. What "Action" is stated there for this
component?
Best regards
Matthias Reuss
-Ursprüngliche Nachricht-
Von: RonnyS [mailto:ronnys.cod...@gmail.com]
Gesende
Hello,
I would like to call some executables from my Burn bootstrapper. I think that
the element is only meant for executables brought as a payload,
not for executables already present on the target machine.
So do you also recommend to implement such a "custom-action-like" call in the
CustomBA
Hi Pavan,
As already stated by Matthew Bobowski, the documentation is somewhat misleading
at this point. The condition for considering the file as modified user data is
NOT
modified date != Created date
But it is
Modified date > Created date
Which means that the file has been modified after
Hello,
Msiexec.exe offers several command-line parameters to tune its behaviour, such
as logging or "UI level". Is there a possibility to specify such parameters
from Burn when starting an MsiPackage?
Best regards
Matthias Reuss
-
Hello,
to my current knowledge, the MSI packages referenced as MsiPackage elements
within a chain must be available at build time, regardless of whether they
shall be compressed into the bootstrapper or not.
Is there a way to circumvent this? Does Burn read vital information (Product
codes etc
compression/etc as well as faster build speeds/etc.
>
> -Original Message-
> From: Reuss, Matthias [mailto:matthias.mr.re...@siemens.com]
> Sent: Wednesday, September 09, 2009 11:29 PM
> To: chr...@deploymentengineering.com; General discussion for Windows
> In
e a hot tip, know a secret or read a really good thread
> that deserves attention? E-Mail Me
>
>
> --- On Tue, 9/8/09, Reuss, Matthias
> wrote:
>
> > From: Reuss, Matthias
> > Subject: Re: [WiX-users] Compression in a Merge Module
> > To: "General discuss
Thanks for your response.
I may have started to handle the issue from the wrong side:
My project consists of several merge modules created with WiX and a "main"
package, which is actually authored with InstallShield. The merge modules are
not addressed in the InstallShield project, so I first b
Hello,
If I want to create a full MSI package, I can set the compression level in the
child of the element.
Can I do similar things when I am creating a merge module? The element
does not have a child...
Best regards
Matthias
--
ld be
> taken care of.
>
> If you don't have VS.Net, then sharpdevelop is free and
> supports creating
> wixproj files.
>
> -Original Message-
> From: Reuss, Matthias [mailto:matthias.mr.re...@siemens.com]
> Sent: Thursday, May 07, 2009 9:59 AM
> T
t; Von: Curtis Jewell [mailto:lists.wix-us...@csjewell.fastmail.us]
> Gesendet: Donnerstag, 7. Mai 2009 16:05
> An: General discussion for Windows Installer XML toolset.
> Betreff: Re: [WiX-users] Running WiX utilities from a script
>
>
>
> On Thu, 07 May 2009 15:59 +0200,
Hi,
As Wix is command-line based, I think it is a good idea to run it from a script.
But: I cannot find any documentation concerning the return values of candle and
light.
Can anyone help?
Best regards
Matthias
--
Th
l
> expression used in subsequent elements.
>
> Chris
>
> > >
> > > From: Reuss, Matthias [matthias.mr.re...@siemens.com]
> > > Sent: Monday, March 23, 2009 10:25 AM
> > > To: General discussion for Windows Installer XML
> > toolset
Hello,
In the MergeModule I am developing with WiX 2, I need Substitution entries in
order to use some properties from the base MSI; however I do not need
Configuration entries because I do not need the module to be configured at
merge time.
The resulting MSM contains a ModuleSubstitution tabl
> -Ursprüngliche Nachricht-
> Von: Bob Arnson [mailto:b...@joyofsetup.com]
> Gesendet: Dienstag, 5. Mai 2009 02:59
> An: General discussion for Windows Installer XML toolset.
> Betreff: Re: [WiX-users] CopyFile: SourceProperty vs. SourceDirectory
>
> Reuss, Matth
Hello,
How do the attributes SourceProperty and SourceDirectory differ?
I expect the SourceProperty attribute to translate into the sourceFolder column
of the MoveFile table. It is described as a Property whose value resolves to
the full path of the source directory. So if I enter any Directory
> -Ursprüngliche Nachricht-
> Von: Bob Arnson [mailto:b...@joyofsetup.com]
> Gesendet: Dienstag, 24. März 2009 18:58
> An: General discussion for Windows Installer XML toolset.
> Betreff: Re: [WiX-users] Character encoding issue
>
> Reuss, Matthias wrote:
&g
ange between MSM and main MSI
>
> Take a look at configurable merge modules in the SDK...
> http://msdn.microsoft.com/en-us/library/aa368027(VS.85).aspx
>
> ____
> From: Reuss, Matthias [matthias.mr.re...@siemens.com]
> Sent: Monday, March
Hello,
When creating a merge module, WiX appends the Module Idto identifiers
wherever it seems appropriate.
However, there are cases where I would like the merge module to use e.g.
property values that have been defined in the main MSI.
Is there any way to do this?
Thanks,
Matthias Reuss
--
Hello,
I am working at a Merge Module project with WiX 2.0.5805.0.
One of its components contains the condition
In the .wixobj file, which is encoded as UTF-8 (at least the header says this),
this condition is still well readable. The "Ö" of "Österreich" is encoded as
0xC396.
When I open th
ssion for Windows Installer XML toolset.
> Betreff: Re: [WiX-users] BrowseDlg: Error2343 (Specified Path
> is empty)
>
> Reuss, Matthias wrote:
> > Unfortunately, neither the error message nor the verbose
> MSI log gives a
> > clue which path might be meant. As far as
Hello,
Is it possible to include a newline character (\n) in a formatted text
string?
I want to output some text containing line breaks in a text control. I
entered the text, using \n for the newlines. The resulting dialog does
contain the line breaks, but also some additional rectangles. What ha
Hi,
I am using the BrowseDlg from WixUI. Instead of displaying this dialog,
the Installer gives a Fatal error "Error 2343.Specified path is empty."
Unfortunately, neither the error message nor the verbose MSI log gives a
clue which path might be meant. As far as I see, the only path needed to
set
28 matches
Mail list logo
