look at WixBA\Bundle.wxs file where authors declare "InstallFolder" as string
variable and they set that variable
within the WixBA.cs code like:
this.Engine.StringVariables["InstallFolder"] = XYZ.
This is the way in which burn relays params to msipackage.
--
View this message in context:
ht
Well ... there you go. Thanks very much.
That just needs to be mentioned in the doc somewhere.
Cheers.
On 12-09-28 03:55 PM, Neil Sleightholm wrote:
> Invoking msbuild against the project file works but so does running candle
> and light e.g.:
> candle -out obj\ *.wxs
> light obj\*.wix
Invoking msbuild against the project file works but so does running candle and
light e.g.:
candle -out obj\ *.wxs
light obj\*.wixobj -o Setup.exe
Neil
-Original Message-
From: Steve Hole [mailto:rsteveh...@gmail.com]
Sent: 28 September 2012 21:06
To: General discussion for Wind
I haven't actually. I can certainly do that, but it seems a bit weighty.
Cheers.
On 12-09-28 01:06 PM, Hoover, Jacob wrote:
> I haven't tried it, but have you tried just invoking the Project or Solution
> via MSBuild?
>
> -Original Message-
> From: Steve Hole [mailto:rsteveh...@gmail.co
When you say "I already have Windows Installer 4.5 listed as a bootstrapper
file", then you aren't using WIX. Are you building an "old" visual studio style
setup project? Are you using InstallShield LE? None of the behavior you are
describing is related to Wix, but rather this other 3rd party
I'm using a few DTF libraries from the v3.6 source code in a project,
specifically Compression, Compression.Cab, WindowsInstaller, and
WindowsInstaller.Package. It's working well, but I think I've either broken
something or there's an issue with resource compilation in those projects.
I first n
Thanks for the reply Jacob. I really appreciate it. However, I am not sure if
I quite understand how upgrading to burn will help me. I already have Windows
Installer 4.5 listed as a bootstrapper file, so how would upgrading to 3.6
help? Also, since I cannot upgrade to 3.6 at the moment, could y
I haven't tried it, but have you tried just invoking the Project or Solution
via MSBuild?
-Original Message-
From: Steve Hole [mailto:rsteveh...@gmail.com]
Sent: Friday, September 28, 2012 1:59 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Building a bootstrapper from the c
I have looked around at some length for a command line interface
definition building a bootstrapper from the command line.
I need to integrate the WiX build process into a larger multi-platform
build management system and need access to the underlying command line
facilities of WiX to do that prop
I am trying, in my Managed Bootstrap Application, detect that my bundle is
already installed and that a few optional features are installed as well. I
wrote the code below, but I never get into the PlantMsiFeature code. I have
set the EnableFeatureSelection on my MsiPackage. Basically, the thi
Hello folks,
is there anything in Burn that provides a possibility to define a minimum and a
maximum bundle version for and upgrade like the -Tags in WiX?
And if not is there a way to handle a check without writing a custom BA?
Overall what is the exact behavior of a bundle that recognizes that
I have rebuilt the patch with the Component marked as Transitive='yes' and
additionally added AND NOT PATCH to the condition but the component still gets
installed.
Is there something about it being a patch that prevents me from changing the
behavior?
Thanks - Tom
-Original Message-
F
Ok, I just tested that. I need to put the CopyFile-Tag into a separate
Component with a neveroverwrite="yes" attribute. Then the file gets updated as
long as there were no changes made to the file. If I change the file and start
an update after that, the file does not get touched by the installe
See my answer on this thread
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-failure-w
hen-using-non-whole-files-td701419.html#a7580582
If files are changed by the user after installation, it's usually preferable
to handle them within the application so that you won't overwrite
Hi Neil,
@1.) Ah... I think I never tested to change the file and then run the update
installer... I will figure that out! Would be nice, if that is the trick :-)
Yes, I need to copy files. We have formular templates that the user can change.
We always ship our default templates as a backup, bu
Hello,
I making patch file with pyro.exe with -delta flag. (Becasue i need
small patch file size). It works well, but some files change by user
after installation (like some data files) and i want to change them too.
But this files can't patch because of changed after installation. So i
need o
1. I think that if the file is changed after a copy then it is not
removed. Do you need to copy the file? If not you could mark it permanent.
2. We use idempotent scripts for SQL so that there is a single SQL script
that can update from any version to the latest.
Neil
>Hey Rob,
>
>thanks for y
Thanks I thought sadly this was the case. Found a work around using check
boxes and twin dialogs..:)
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 28 September 2012 03:56
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] cust
Thanks Rob, Il give that a go..:)
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 28 September 2012 04:09
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Overwrite MSI Error Messages
I think the Error element lets you do this
Hey Rob,
thanks for your answer.
@1.) Yes, I did so and sadly the copied content gets removed :-( So I assume I
will write a CA that handles the copying and take the responsibility for the
files away from WiX.
@2.) Yes, that sounds like a good idea - as I do not know the scripts very well
yet
20 matches
Mail list logo
