Hi
Could anybody help me with fragments and features. I'm working on big wix
project with lot of fragments.
Idea was that I make libraries for everything what can be shared between our
installers and then just by references compose what I need.
Everything goes fine until now. I created fragment (
Yes, I am. I'm not sure exactly which Visual Studio or Windows SDK versions
have that particular package. There's probably a list out there somewhere.
Dave
On Tue, Sep 20, 2011 at 4:13 PM, John Bergman [via Windows Installer XML
(WiX) toolset] wrote:
> Thank you. Are you working with VS2010?
Are you building Projects that exist in VS2008 or 2010? If so, we simply
created the WiXprojects and it was all handled automatically.
In our case, we created a separate project that handled the build of the
install packages, using MergeModules from several places, including some of our
own.
Thank you. Are you working with VS2010?
-Original Message-
From: Dave Andersen [mailto:d.ander...@gmail.com]
Sent: Tuesday, September 20, 2011 5:03 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Anyone have a sample WixProject that includes
installing and configuration
The simplest way is to use Votive to generate a .SLN / .WIXPROJ and then
add the sln configuration | platform to to the build parameters in the
build definition. You shouldn't have to do any customizations in workflow
as the Default Template will work out of the box. Passing a
ProductVers
I need to build some MSIs with Wix during our TFS build. Our current TFS build
is using the Windows Workflow XAML files to declare the build logic. What's the
best way to invoke Wix from there? Directly invoking the process from an
activity? Going down to a powershell script and calling it from
We package SQL Express as a prerequisite using .NET bootstrapper.
You can find the package if you have the SDK installed somewhere like this
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages
We needed to make some modifications to the default package details to
provide a S
Thanks John for prodding me in the right direction. After looking around a bit
more (particularly Peter Marcu's blog entry of 30-May-2008) I did admin
installs such as the following :
"msiexec /a orig\setupproject1.msi TARGETDIR=c:\wix\admin"
"msiexec /a new\setupproject1.msi TARGETDIR=c:\wix\
As the error message implies, you need to do an /admin install of the MSI
before running pyro/torch so that it has access to the files if you don't want
to use wixpdb's.
--
John Merryweather Cooper
Jack Henry & Associates, Inc. (Premier Tech, Inc.)
Build & Install Engineer - jXchange
Office: 91
Hi all - I've been experimenting with torch/pyro/patching on our Wix installer,
which I'm proud to say has completely replaced InstallShield for our
application.
The thing I'm wondering about is this: do you have to use .wixpdb files as
input to torch, or can you use .msi's instead ? The docs
Hi all,
i want to create a msi package with a daemon / service configuration,
but the installation of the service fails. To be more clear, the files
are copied to the right place and even the firewall rules are working.
But the service ... no chance. I tested the msi package in XP SP3,
Server 2003
You can set Property/@SuppressModularization attribute. However this is
described as a last resort :)
You can also use configurable merge modules but they are a pain.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/avoiding-GUID-d
ecoration-in-merge-module-property-name-td5742531.htm
Hi all,
I'm implementing an installer using merge modules. Two of these
modules contain ServiceInstall elements like this:
One of the modules has platform="x64", the other platform="x86" -
otherwise I would use only one module.
The properties are both marked Secure="yes"; the password property h
13 matches
Mail list logo
