After receiving emails from people on this subject asking about our
process, I will reply to all publicly here.
Unfortunatly my employer 'owns' the code, getting OS in the door is hard
enough, getting it out is not an option I am afraid.
However for those interested the general methodology used
Although Rob et al, don't recommend this approach we have been using
Heat, and it's predecessor, as part of our automated build process for
over a year with Wix3.
The main things to be wary of are the spurious entries generated by
Heat, for example VB6 entries which should not be there.
However t
I am trying to be nice to users upgrading from one version (or rolling
back) and use the general method of creating a default value which the
user can override in the install, or may override by editing the
registry value itself later on (perfectly valid in the context of the
applications, things c
next build then.
Peter
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 07 November 2006 16:01
To: Dyson, Peter
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Com LocalServer32 in 8.3 format
Dyson, Peter wrote:
> I am currently using v3.0.1703.0 a bit
I am currently using v3.0.1703.0 a bit old in the tooth now but have not
had time to use any later.
Peter
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 07 November 2006 03:34
To: Dyson, Peter
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Com
Hi,
I am authoring wix version 3 com servers in the 'correct' way as below,
but the LocalServer32 @ registry entry is generated in 8.3 format names.
This seems to be because of the [!MyServer.exe] generated in the msi. If
I use orca to change that to [#MyServer.exe] then I get the long
filename a
6 matches
Mail list logo
