I am wondering about how to best create my installer, and is looking for
some advice on this from the experienced people on this list.
A bit about the system I am shipping:
Software Requirements
===
(These will be handled by either a bootstrapper or manually by the
person performi
I've got a custom install project where I have overridden the
Wix_UI_InstallDir.wxs because I did not want the
ARPNOMODY set to one. I've created a CustomUI_InstallDir.wxs that is very
close to the original document with
A couple of exceptions.
I've remove the APRMODIFY. I want my install to g
Check out Parafin.
On Dec 11, 2009 11:34 AM, "Sankaranarayanan" wrote:
Hi,
Whats the best way to include all files from a source folder and deploy them
onto a target folder during installation.
Currently I have separate and elements for each source
file in the wxs file - whenever a new file
On Dec 11, 2009 11:34 AM, "Sankaranarayanan" wrote:
Hi,
Whats the best way to include all files from a source folder and deploy them
onto a target folder during installation.
Currently I have separate and elements for each source
file in the wxs file - whenever a new file is added in the sour
WiX doesn't support dynamically including files, however you can run
heat to generate a wxs each time prior to calling candle/light.
On Sat, Dec 12, 2009 at 6:32 AM, Sankaranarayanan wrote:
> Hi,
>
> Whats the best way to include all files from a source folder and deploy them
> onto a target fol
Jeffrey Bindinga wrote:
> In the logfile I see that the property is set on the UI and the INSTALL (no
> typo's either), but my condition still evaluates to false while
> DEPLOYMENTTYPE is AllInOne.
>
See http://www.joyofsetup.com/2007/05/30/feature-conditions-and-ui/.
--
sig://boB
http://joyo
Robert Hermann wrote:
> In my wix program I have set ARPNOMODIFY to 0 which prevents doing it through
> ARP.
>
>
>
> But when I compile I get this error what am I doing wroing
>
> Error 2 The primary key 'ARPNOMODIFY' is duplicated in table
> 'Property'. Please remove one of the
Jerry Maloney wrote:
> I have created an MSI using WiX. I now have an issue with the displayed file
> size in the Custom Setup screen. I have 9 features to install: the core
> files, plus 8 optional files. These optional files are quite large, between
> about 60 and 150 MB each. The issue is
Sean Farrow wrote:
> Within the netfx extension (cost.h) what is the value:
>
> const UINT COST_NGEN_NONBLOCKING = 500;
>
> used for? What is this value used for and how is this value arrived at?
>
See the MSI SDK topic "Adding Custom Actions to the ProgressBar."
--
sig://boB
http://joyofsetu
Thanks
I think I understand the picture
Giora
Blair wrote:
> The intent is:
> - A major update is an update that "replaces" all previous versions of a
> product. It never requires (usually) the previous version to be installed.
> - A minor update is an identical copy of an original with some "m
10 matches
Mail list logo