y to NOT automatically
> update
>to a new version, but stick to a specific version. This way, you control
>when to update.
>
>
> Kind regards,
>
> Wilbert van Dolleweerd
> http://gplus.to/WilbertVanDolleweerd
>
>
> On Wed, Jul 10, 2013 at 12:19 PM, a
I'm really confused by where NuGet fits in with a WiX deployment (which you
can guess by the questions at the end...)
Currently we’re really happy with our WiX (3.6) setup (smile)...
Our TeamCity build creates the installers using Burn and Neils burn UI
customisations for our WinForms products th
I've defined the following MSIPackage in a chain (burn 3.6)
http://ourURL.com/updates/x86/DACFramework.msi";
Compressed="no"
Vital="yes"
Permanent="yes"
SuppressSignatureVerification="yes"
Visible="yes"/>
To my understanding, making it Vital an
e issue by adding the
> SuppressSignature attribute (it's called something like that) to the
> MsiPackage element.
>
>
> On Wed, May 29, 2013 at 6:30 AM, andy smith wrote:
>
> > Using Burn 3.6, I'm trying to install three Microsoft MSI's (The SSDT
> May
> > 20
Using Burn 3.6, I'm trying to install three Microsoft MSI's (The SSDT May
2013 Update -
http://blogs.msdn.com/b/ssdt/archive/2013/05/03/sql-server-data-tier-application-framework-may-2013-available.aspx)
When attempting to install these files, on two of them I get the same error
-
0x8009200d - N
No. I didn't know this was something I needed to do & haven't done so
before...
On Tue, May 28, 2013 at 4:22 PM, Rob Mensching wrote:
> Have you modified the InstallExecuteSequence in your MSI?
>
>
> On Tue, May 28, 2013 at 5:32 AM, andy smith wrote:
>
> >
Hi, I have a wix 3.6 install using burn.
One of my MSIPackages (SharedDX.msi) within the setup fails to install.
In the overall log I get..
[0814:0E98][2013-05-28T11:15:54]: Applying execute package: msi_SharedDX,
action: Install, path: C:\Documents and Settings\All Users\Application
Data\Packag
I have a burn 3.6 installation with a number of packages in the chain. One
of the MSIPackages I want installed no matter what other msi packages are
each time, and therefore have forced the InstallCondition to "1"
http://oururl.
../setupsharedcomponents.msi"
DisplayName="Shared
I have a WiX 3.6 install using burn to chain 5 packages plus a
pre-requisite of .net 4 which uses the short but sweet
reference. It's working pretty nicely,
but there is one area which needs tidying up.
Three of my packages (which are installed into their own separate
directory) have a large num
I have a burn installer, whereby the original installer can effectively
select which items to install via checkBoxes, which relate to individual
msi's.
These are working via InstallConditions, checking the fact that the
checkbox has been checked, and that they are not installed. So far so good
and
10 matches
Mail list logo
