So, when using burn, I could use the bootstrapper application to set a
"OriginalBootstrapper" Property and copy that to the desired path. Is
there a burn variable for the original file?
Am 27.05.2011 06:56, schrieb Blair:
> WiX's element can copy arbitrary files to arbitrary directories.
> You
There is not current code in WiX to set arbitrary permissions on
certificates installed via WiX.
If someone can dig up the APIs used to set permissions on certificates, that
could be added
-Blair
-Original Message-
From: Will Gross [mailto:mastermind...@gmail.com]
Sent: Wednesday, May
What does a verbose log say? If you are not certain as to the value of your
IUSR_USERNAME property, it will be hard to verify that what account was
given write access to your file.
-Blair
-Original Message-
From: gapearce [mailto:mr_gapea...@yahoo.com]
Sent: Wednesday, May 25, 2011 12:42
Explain "not included in the patch", because I have three very different
ideas that you could be referring to.
1) Is this based on opening the MSP file in Orca?
2) Was there an error when applying the patch to an already installed
product?
3) Are you referring to running SQL against the MSP file i
WiX's element can copy arbitrary files to arbitrary directories.
You can reference the installation MSI via the OriginalDatabase Windows
Installer property.
-Blair
-Original Message-
From: Michael Stoll [mailto:unwicht...@mistoll.de]
Sent: Thursday, May 26, 2011 5:23 AM
To: wix-users@li
All three can be done, yet I do not recommend #3 at all (just don't do it).
Use Windows Installer properties to implement #1 would best meet your goals.
If you don't put any condition on the custom action you use to generate your
properties, it will run every time (install, remove, repair, upgrade,
The project reference does two things:
1) It generates WiX preprocessor (candle) variables relating/referencing the
project:
http://wix.sourceforge.net/manual-wix3/votive_project_references.htm
2) If you set Harvest to True, it uses the Project Harvester (the "project"
argument to heat) to generate
Hi,
I'm writing an installer for an excel addin. In order to register the
addin, with excel, I need to add an entry under a registry key. The entries
are named OPEN, OPEN2, OPEN3 ... sequentially for each addin that is
registered.
Because many addins could have been installed by the user before
Thank you for your answer.
Even the engine is very important, I think it is a bit annoying when we cannot
display the current msi name during the progress. We are starting to use burn
now in our official releases and I hope you could raise the priority of this
bug.
Synopsis: The package name
I'm using WIX 3.6 with burn for deploying a client/server application.
On the server there's a file share for the client setup files. Thus the
server setup routine should copy the setup files for the client to this
file share.
Is there a best practice for solving such a setup scenario?
Currently
Hi,
I am using Wix 3.5.2519.0 to create patch. I am unable to execute SQL script
from patch. I am adding reference to the binaty stream of SQL file in patch.
But the binary is not included in the patch.
Thanks in advance.
--
View this message in context:
http://windows-installer-xml-wix-toolset
Do a google search for "wix project references" make sure you are directed
to the appropriate version of the wix doc (wix 3, for example), then
bookmark it. I have referred to that page many times.
On May 26, 2011 3:10 AM, "news.gmane.com" wrote:
> Does anybody has a suggestion?
>
>
> "Andreas" w
Does anybody has a suggestion?
"Andreas" wrote in message
news:irgpfi$7pn$1...@dough.gmane.org...
> Hello,
>
> I hope I am here at the right place for this question.
>
> I added a WiX project to a Visual Studio solution. Then I added a
> reference to the C# project in the same solution. In the
13 matches
Mail list logo
