Hello,
I use heat.exe to harvest a folder located outside the Msi-project.
This is my current output in the generated wxs-file.
File Id=... KeyPath=yes Source=$(var.ThePath)\a\b.txt /
In this case I need to set up var.ThePath in the project as pre processor
variable (or use WiX-variable set up
You could use a bind path (named or unnamed), which I have seen recommended
over the use of preprocessor variables in this forum.
Unnamed bind path:
file source would be:
File Id=quot;...quot; KeyPath=quot;yesquot; Source=quot;\a\b.txtquot;
and in wixproj or in Properties/Tool
Apologize as this is a bit off-topic - actually it is a general MSI
question. However, I couldn't find any other forum on the net to ask this
question. Also, this has been asked a few years ago in this forum, but there
was only one quite fuzzy answer. BTW, I'm only interested in MSI 5+.
I'm
Yes!
I then got:
File Id=... KeyPath=yes Source=*SourceDir*\a\b.txt /
2015-04-17 12:20 GMT+02:00 Nir Bar nir@panel-sw.com:
Have you tried not specifying a variable to heat?
-
Nir Bar
Freelance Developer
Mail: nir@panel-sw.com
Web: www.panel-sw.com
- C++ On Windows, Linux
Have you tried not specifying a variable to heat?
-
Nir Bar
Freelance Developer
Mail: nir@panel-sw.com
Web: www.panel-sw.com
- C++ On Windows, Linux and Embedded Platforms
- WiX InstallShield
--
View this message in context:
It continues the installation. It will set the RESUME property, and
properly authored UI installs will show a Resume dialog saying that
the install is resuming.
---
Phil Wilson
On Fri, Apr 17, 2015 at 3:03 AM, Martin Cornelius
martin-cornel...@t-online.de wrote:
Apologize as this is
Hi Phil, really interesting. But when does that happen ?
- Automatically after System Restart ?
- Automatically Once anybody logs on
- Automatically Once an Administrator logs on ?
- Once someone manually execuetes the MSI ( that's what I guess) ?
Why doesn't that work today?
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Martin Cornelius [mailto:martin-cornel...@t-online.de]
Sent: Friday, April 17, 2015 12:54 PM
I know this has been asked before (and answered as 'impossible'), but
perhaps something has changed during the last 6 months ?
We're envisioning to create an Installer that uses Burn - for two reasons:
- we'd like to check for prerequisites and install them
automatically
-
I am also facing the same issue in 3.9 RC2. Still the bug exists. What would
be the workaround fr this?
Regards,
Sampat
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Could-not-harvest-data-from-a-64bit-dll-tp5511948p761.html
Sent from the
10 matches
Mail list logo