Something's not making sense. Properties like [WindowsFolder] are stored
directly in the MSI and are resolved at install time. Were you simply using it
as a path in something like a <File> element? What do the install logs show
when you run the MSI on the target machine?
Neil
________________________________
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Greg Silin [EMAIL
PROTECTED]
Sent: Tuesday, July 29, 2008 7:12 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Building msi across OS's
Rob,
Thanks for the advice. Unfortunately, my experience was that when
[WindowsFolder] was used, it would resolve on the machine where the code *was
compiled*. Since I built my code on the client (which might not be a smart
choice anyway, but that's a different story), it resolved to C:\Windows in the
wixobj file. That will not work on the Win 2003 OS.
Am I doing something wrong?
Thanks
-greg
-----Original Message-----
Date: Mon, 28 Jul 2008 20:45:25 -0700
From: Rob Mensching <[EMAIL PROTECTED]>
Subject: Re: [WiX-users] Building msi across OS's
To: General discussion for Windows Installer XML toolset.
<wix-users@lists.sourceforge.net>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
You don't need a CustomAction. The Windows Installer has built in variables
for a great many paths in Windows. WindowsFolder in this case. MSI SDK lists
them all.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Silin
Sent: Monday, July 28, 2008 16:48
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Building msi across OS's
Hi,
Question from a wix newbie.
I ran into the following issue:
I am building an msi in Vista (let's just say client) that could be installed
either on Vista (client) or Win 2003 Server OS. One of the issues was that the
framework resides under C:\WINNT in the server OS, and under C:\Windows in
client (vista in my case).
Apparently, any environment variables in wxs are resolved at compile, not run
time. Is the only way to make it possible to use one MSI to do a CustomAction
that first determines which of the OS's I'm running on and then attempt to set
the property? Is that even possible?
Thanks for any tips :)
-greg
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net<mailto:WiX-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
