Hmm, ok. That's a bummer that they started putting parenthesis in there.
There are several workaround for the issue (set another env var, hard-code
the path, etc...). Could you open a bug in WiX 3.0 indicating that
environment variables with parenthesis won't work?
Thanks,
Derek
-Original M
Derek:
The value is being used at build time to determine the location of
the appropriate merge modules for Visual Studio 8 run times.
Jeffrey Altman
Derek Cicerone wrote:
> Sorry for all the questions, here's one more: how is the value of the path
> to Program Files (x86) being used? This val
Sorry for all the questions, here's one more: how is the value of the path
to Program Files (x86) being used? This value is specific to the build
machine so it wouldn't be useful in the MSI file since the machine on which
the msi is being installed may use a different path. You'd want to use
some
That is a standards Windows environment variable on 64-bit Windows
builds within the WOW64 environment.
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
Jeffrey Altman
Derek Cicerone wrote:
> Nested parenthesis is unsupp
Nested parenthesis is unsupported in both versions of WiX. Is that a
standard Windows environment variable or one which you are defining?
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeffrey Altman
Sent: Tuesday, July 18, 2006 4:36 PM
To: wix-us
In build 2419 it was possible to evaluate the value of the environment
variable
CommonProgramFiles(x86)
within a define as such
In 2.0.4310.0 this is broken as the close parens are no longer matched
with the open parens.
Are there any quoting rules that can be used to make this work in th
I have had problems where I used a property to specify the
web address and because the property was not set at uninstall time, the
uninstall failed.
The trailing // in the key makes me suspect that you may
have created a virtual directory whoose name came from a property. At uninstall
time
I’ve gotten my website to install and now I’m
getting an error trying to uninstall the website.
“Failed to delete metabase key: /W3SVC/1/Root//”
Has anyone experienced this before?
__
Don Tasanasanta
VIACK Corporation
425-605-7423
OK, thank you.
I simply wrapped the component directory tree with:
...
and all is well.
--
View this message in context:
http://www.nabble.com/merge-module-installation-location-tf1955504.html#a5381370
Sent from the wix-users forum at Nabble.com.
-
We're struggling with a problem, and I'm curious if anyone has any
creative solutions they can think of.
We have a windows service that our MSI installs. This service does some
things with MSMQ. We want to ensure that our service has the
appropriate ServiceDependency so that Windows starts thing
Sorry didn't post my reply here before.
That article was perfect but I have one question. I can get my DLL to
execute just fine in the InstlallUISequence but as the author states if the
install is a silent install then this action wont fire. I have tried to
place it in the InstallExecuteSequence
In terms of getting the DLL working, this is a good guide.
http://www.codeproject.com/tips/msicustomaction.asp?df=100&forumid=3159&exp=0&select=785495
It doesn't show you how to do what you want in the DLL, but it does show you
the steps needed to get
one working. As for the actual code, do you
12 matches
Mail list logo
