Ahh, that makes sense. The example I read didn't... but of course I was
calling you Brian so who knows what I was really thinking.
On Fri, Dec 18, 2009 at 2:28 PM, Markus Gaugusch wrote:
> Hi Rob,
>
> (You probably ment me, because I don't know who Brian is ;-)
> I needed to set a property to t
Hi Rob,
(You probably ment me, because I don't know who Brian is ;-)
I needed to set a property to the value of an environment variable because
I wanted to populate an input field with it. I didn't see any other
solution.
Markus
On Dec 17, Rob Mensching wrote:
> Brian, Why are you using a Pr
these patterns in creating your
registry entries.
Otherwise, use [%env-var].
-Original Message-
From: Markus Gaugusch [mailto:w...@gaugusch.at]
Sent: Tuesday, December 15, 2009 10:52 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Expanding an env
Brian, Why are you using a Property to set another Property? Why not just
use [%MY_ENV_VAR] where you would use [MY_ENV_PROPERTY]?
Bruce,
1. You can refer to the install location of a file in your MSI using the
[!FileId] syntax.
2. Under ProgramFilesFolder is where you should install your appli
On Dec 15, Bruce Cran wrote:
> I've written an installer with WiX 3.5 which installs a Winsock
> provider, netsh helper and a kernel driver. After doing some
> restructuring I started getting a warning about installing a
> non-permanant component into system32, so I'm now trying to change the
>
I've written an installer with WiX 3.5 which installs a Winsock
provider, netsh helper and a kernel driver. After doing some
restructuring I started getting a warning about installing a
non-permanant component into system32, so I'm now trying to change the
installation location to be under %Progra
6 matches
Mail list logo
