If this file needs to exist before the installation is ran, you could have
something like:
<Property Id="FILEEXISTS">
<FileSearch/>
</Property>
And if the FileSearch succeeds, FILEEXISTS would be set to true. Then you
could have a <Condition/> that won't let the install proceed if it isn't
set? I've done this with a <RegistrySearch/> before.
On 1/29/07, Ian Couper <[EMAIL PROTECTED]> wrote:
I would like to use the FileSearch property to trigger a rollback if a
particular file is not located. I know how to use the FileSearch property,
but not hot to force a rollback based on its outcome. Can anyone help me
with this one, or point me in the right direction?
Thanks
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
