with any
serious commercial package."
Most serious commercial packages that I can think of actually use some kind of
setup.exe bootstrapper. I have never purchased any boxed software, for example,
and launched an msi directly. The setup.exe can detect if a minor upgrade needs
to be launched
I'm keen to avoid doing that since it means creating the bootstrapper. It just
doesn't seem quite right to me to have to do that.
Thanks for the suggestion, but I think for now I'll stick to changing the
product Id. Do you know if there's any undesirable side effects to doing this?
Cheers,
Ad
2008 18:04
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major)
affect file overriding?
Product/@Id="*"
-Original Message-----
From: Adam Connelly [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 08
The project I'm working on at the moment uses a build server to automatically
build our installers, etc. As part of this, it provides the version number to
the installer. Therefore, every publish we do (and in fact every checkin of
source) is a different version of the product. This means tha
Hi,
I'm building an installer and it was going good until I wanted to add a new
dialog. I now want my installer to be able to install some "extensions" into a
third party application directory, and therefore want to have a dialog that
allows users to specify the installation directory. I'm us
let me know and I'll do what I can.
Chris
On Mon, Aug 18, 2008 at 9:33 AM, Adam Connelly <
[EMAIL PROTECTED]> wrote:
> Hi,
>
> Just wondering if Wix has anything built in that allows a user to select an
> Sql server database (with windows / sql authentication, etc). I'm
Hi,
Just wondering if Wix has anything built in that allows a user to select an Sql
server database (with windows / sql authentication, etc). I'm sure I've seen
this in installs before (something similar to the connect dialog in management
studio).
If not, I take it that I have to write somet
> Neil
>
> Neil Sleightholm
> X2 Systems Limited
> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>
>
>
>
> From: [EMAIL PROTECTED] on behalf of Adam Connelly
> Sent: Fri 18/07/2008 11:30
> To: wix-users@lists.sourceforge.net
&
Hi,
I've got a CI setup that automatically generates a x.x.x.x style version
number. I've got all my assemblies versioned properly (with a generated shared
SolutionInfo.cs file), and I set the msi output name as MyMSI-x.x.x.x.msi and
now I want to set the Version attribute of the Product tag.
ED] [EMAIL PROTECTED] On Behalf Of Adam Connelly [EMAIL
PROTECTED]
Sent: Thursday, July 17, 2008 6:29 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Wix and MSBuild
I actually sorted the problem (a typo :(). I would still be interested to find
out how ot
I actually sorted the problem (a typo :(). I would still be interested to find
out how others structure their projects.
Adam
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adam Connelly
Sent: 17 July 2008 11:19
To: wix-users@lists.sourceforge.net
Hi,
I currently trying to add a task into my MSBuild file that will create the
various MSI files needed for the project. I've got the following file
structure:
Root/
Build.xml
Code/
Deploy/
ProjA
ProjB
Installs/
ProjA.wxs
Sorry if that's not amazingly clear. Basical
12 matches
Mail list logo
