Oh darn, well it seems that I maybe able to use the version number of
one of the files these chaps install, so maybe it won't be so bad after
all, Thanks Rob.
Simon
---------------------------------
Message: 5
Date: Tue, 20 Jan 2009 10:38:10 -0800
From: Rob Mensching <rob.mensch...@microsoft.com>
Subject: Re: [WiX-users] condition on a feature, greater than or equal
to
To: General discussion for Windows Installer XML toolset.
<wix-users@lists.sourceforge.net>
Message-ID:
<de33023b477fe44eaa71983f5279f6ce50fc4f5...@na-exmsg-c102.redmond.corp.m
icrosoft.com>
Content-Type: text/plain; charset="us-ascii"
Yep, what you're seeing is known. The Windows Installer will convert
Property values to numbers for you when doing comparisons... but only if
the data provide is all digits. The # in front of DWORDs from RegSearch
is maddening for this reason. Bob has a design laying around somewhere
for completely replacing AppSearch with a data driven CustomAction that
is more powerful and more useful but that's not in development anywhere.
So, you need to do something to tweak the DWORD into a number (sadly, I
think that means CustomAction).
-----Original Message-----
From: Simon Topley [mailto:simon.top...@wallingfordsoftware.com]
Sent: Tuesday, January 20, 2009 08:27
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] condition on a feature, greater than or equal to
Hello all, its' been a very long time since I checked in here. I've
joyfully had an issue with our installers of late that should be simple
to solve... only I can't solve it.
The situation is this, our clients install many versions of our software
new and old and run them concurrently. We also ship third party drivers
for our dongles, so users have to have a valid license to use our
software. Now the most recent update of this third party install has
raised a weird issue that we haven't seen before. When someone installs
an older version of our software alongside the newest version the older
driver mangles the newer one as I assume it is still attempting to
install it.
I get the version number for this third party software from the registry
using a property, as raw - its' a DWORD in the registry. Now I'm hoping
I can just done some simple comparison like this (on the feature)
<Condition Level="0">DRIVERVERSION >= "7"</Condition>
Sadly this doesn't work as the version number has a hash in it as I got
it as raw, and I think it maybe comparing it as a string anyway. I'm not
sure I can even use a greater than or equal too in a condition like this
anyway. I'm dying here please help!
The information contained in this e-mail is likely to be confidential
and
may be legally privileged. It is intended only for the addressee. If you
have received this message in error please notify the sender immediately
at
the above address. The disclosure, copying or distribution of this
message
or its contents without the prior approval of Wallingford Software is
strictly prohibited. Wallingford Software is not liable for
unauthorised disclosures nor for subsequent actions or omissions in
reliance
upon them.
Registered in the UK, company no: 02288719
Wallingford Software Limited, Howbery Park, Wallingford, Oxfordshire,
OX10 8BA
------------------------------------------------------------------------
------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------
Message: 6
Date: Tue, 20 Jan 2009 10:48:21 -0800 (PST)
From: Improvize1 <improvi...@yahoo.com>
Subject: [WiX-users] ScheduleReboot and Post-install Bootstrapper
To: wix-users <wix-users@lists.sourceforge.net>
Message-ID: <82447.77519...@web111112.mail.gq1.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Hi,
Our installer is packed with a post-install bootstrapper that runs
installs some additional software if it is not already present on the
target machine. (That is, it may or may not run.) The main setup also
has a ScheduleReboot action before InstallFinalize. We are running into
a problem where the reboot and bootstrapper dialogs appear at the same
time. Any suggestions for how to remedy this?
Thanks!
------------------------------
Message: 7
Date: Tue, 20 Jan 2009 13:52:59 -0500
From: Alicia Holloway <ahollo...@sounddes.com>
Subject: [WiX-users] How to add an Operating System specific shortcut
To: wix-users@lists.sourceforge.net
Message-ID:
<ca2eea2e0901201052h47371402je7942e7a48648...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hi,
I have a Wix project in which I am trying to add a shortcut to a command
prompt which calls a batch file as a command line argument. With the
code I
have so far (see below), I can get it to work on Windows XP only,
because
the environment variable it's using to find the cmd.exe program is
determined at compile time (and it's being compiled on an XP).
It doesn't work on Windows 2000 because the system32 directory is not
under
"Windows" but rather, under "WINNT". The shortcut appears on the start
menu
on Windows 2000 systems but, clicking on properties displays the line:
"C:\Windows\System32\cmd.exe /k projectvars.bat"...so it can't find
cmd.exe.
Product.wxs:
------------------
<Property Id="COMMANDPROMPT">$(env.WINDIR)\system32\cmd.exe</Property>
(alternatively, $(env.ComSpec) could be used instead of
$(env.WINDIR)\system32\cmd.exe)
Files.wxs:
--------------
<Shortcut Name="Project Command Prompt" Target="[COMMANDPROMPT]"
Arguments="/k projectvars.bat" Id="CommandLineStartMenuShortcut"
WorkingDirectory="BinFolder" Icon="ProjectVarsIcon.exe"
Directory="ProjectToolsProgramMenuFolder">
<Icon Id="ProjectVarsIcon.exe" SourceFile="cmd.ico"/>
</Shortcut>
Is there any way to modify this code so that it determines the value of
the
environment variable at runtime? Or, is there a way of setting a
different
filepath so that it uses the Sys32Folder property somehow? I briefly
attempted to change the property to:
<Property Id="COMMANDPROMPT">[Sys32Folder]\cmd.exe</Property>
to see if that could work...but was given the following warning when I
tried
to compile it:
"If this value is a string literal, not a property reference, please
ignore
this warning. To set a property with the value of another property, use
a
CustomAction with Property and Value attributes."
But wasn't able to figure out how a CustomAction would apply in this
situation.
Any help would be greatly appreciated!
Best Regards,
Alicia
------------------------------
------------------------------------------------------------------------
------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
------------------------------
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
End of WiX-users Digest, Vol 32, Issue 92
*****************************************
The information contained in this e-mail is likely to be confidential and
may be legally privileged. It is intended only for the addressee. If you
have received this message in error please notify the sender immediately at
the above address. The disclosure, copying or distribution of this message
or its contents without the prior approval of Wallingford Software is
strictly prohibited. Wallingford Software is not liable for
unauthorised disclosures nor for subsequent actions or omissions in reliance
upon them.
Registered in the UK, company no: 02288719
Wallingford Software Limited, Howbery Park, Wallingford, Oxfordshire, OX10 8BA
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
