No. The ProductName property is immutable once the installer begins.
You'd have to do something like asking for the name before starting
the install and then dynamically generate and apply a transform for
installation.
Hi, would anyone have any examples of this?
-Original Message-
Date: Thu, 30 Aug 2012 18:03:02 -0400
From: mukeshj...@kpmg.com
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Major Upgrade changes requirement
What changes we need to do for Major Upgrade
Example - Product Code, Package Code, version
That's not what I've found. I've got a custom action running which
changes our ProductName at install time in WiX 3.5. It is one our first
actions in our InstallExecuteSequence and seems to work. All the Actions
before it need to not reference [ProductName] or else get the 'wrong'
result. Can
Hi,
I've thought about this a great deal and would like to know some of your
opinions.
I'm creating many installers for our company but we don't know some of the
names of the products etc at build time. I was thinking of creating one
generic installer and have the many transform files
I remember looking at this many years ago and the observation and consensus
was that you couldn't change it. That MSI read it in when it initialized
and that was that. Maybe it does warrant reexamining as it'd be useful in
multiple instance scenarios (think named instances ).
I know the MSDN
Are you NC1 on Stack Overflow?
From: Natalie Carr natalie.c...@measuresoft.com
Sent: Friday, August 31, 2012 4:50 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Transforms and 1 generic installer
Hi,
I've thought about this a great deal
That's me. I'm hoping to recreate what you advised me to do and propose this
as it is a far better option that what I have currently and leaves the
installers to be easily modified for future products. Thanks
-Original Message-
From: Christopher Painter [mailto:chr...@iswix.com]
Sent: 31
I've found it conceptually much simpler (at least at first glance - we're just
entering beta) to build a front end that generates the WXS files on the fly for
various things we install (though keeping track of DirectoryRefs and such is a
pain) and then calls the WiX tools behind the scenes for
See: http://robmensching.com/blog/posts/2012/8/21/Enter-WiX-v3.7-toolset under
New Build System
On Thu, Aug 30, 2012 at 8:15 PM, Sean Farrow
sean.far...@seanfarrow.co.ukwrote:
Hi:
The dtf.chm is in the source zip for 3.7, but does not seem to be in the
3.7 install or the binary zip, is this
I may not fully understand your requirements but I would not push work that
can be done at build time to install time.
On Fri, Aug 31, 2012 at 6:14 AM, keith.doug...@statcan.gc.ca wrote:
I've found it conceptually much simpler (at least at first glance - we're
just entering beta) to build a
Hi, yes I am just going to use transforms to change product name, manufacturer
name, etc. Is there issues between GUID's in transforms?
Thanks Rob
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 31 August 2012 15:46
To: General discussion for Windows
Assuming you want them to be able to install multiple instances of the same
MSI with different destination folders, then you would want to look at the
MultiInstance=yes attribute on components. I know I had suggested a patch a
while back to allow for some better handing
12 matches
Mail list logo
