Phil,
your sample code works for me as well. Off to see where mine is different...
On Mon, 2 Sep 2013 10:25:03 -0700, Phil Wilson wrote:
> My dumb search works just fine - I can't see what the issue is. This works
> for me:
>
> Sample.msi and thing.txt in the same directory.
>
>
> Id="CheckF
It will work only during first install, as Rob most likely knows. During
repair, feature change, and uninstall the SourceDir location is (IIRC) the
installer directory of the cached MSI file.
It's not good design to rely on external files in the same location as the
MSI. There are too many failure
My dumb search works just fine - I can't see what the issue is. This works
for me:
Sample.msi and thing.txt in the same directory.
and a custom action in the execute sequence to display the value...
msgbox
session.property("FILEEXISTS
I searched for WiX FileSearch in same directory as MSI on google. The
first hit [1] I received [2] includes a reply from Phil Wilson
suggesting the SourceDir [3] or OriginalDatabase [4] (with some
additional parsing) might work.
[1]
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/H
Hi Edwin,
no need to be suspicious of Depth and AssignToProperty (firstly, omitting them
didn't improve
things, nor did I expect it to) as Depth can avoid unnecessary file system
traversal (don't know how
deep the search would go if no Depth is specified but would assume that default
should b
I'm highly suspect of the values for the Path, Depth and
AssignToProperty attributes in your DirectorySearch.
The example sent by John Cooper, replicated below for convenience,
didn't set AssignToProperty="no" nor Depth="0".
Hi John,
I don't think so - I understand that perfectly. As I wrote in my post "...
where both the MSI & the
inifile reside ..." - the ini file sits right beside the MSI at the time of
execution, yet it is not
found by my Wix code, regardless of how I specify the directory for it;
absolute pa
I suspect part of your problem is your concept of what a DirectorySearch or
FileSearch does. Both searches look for directories and files that already
exist at the time of the install. For example, I use a FileSearch to recover
the path to a web.config so I can recover it's encrypted connectio
that means that I didn't actually do smth wrong in the code, it's just
that I can't really control that?
On 4/28/2010 12:50 PM, Blair wrote:
> Unfortunately with MSI's AppSearch action, you don't have any real control
> over the order of the attempted resolution of each of the various
> propertie
Unfortunately with MSI's AppSearch action, you don't have any real control
over the order of the attempted resolution of each of the various
properties.
-Original Message-
From: Viv coco [mailto:vcotirl...@hotmail.com]
Sent: Friday, March 26, 2010 2:18 AM
To: WiX
Subject: [WiX-users] File
d, "InstalledProductName")
a.Writeline (" " & pname & " " & prod & "and is installed at " & pid)
Next
Next
Phil Wilson
-Original Message-----
From: Eric Napier [mailto:napi...@gmail.com]
Sent: Wednesday, July 22, 2009 1:45 P
-Original Message-
From: Eric Napier [mailto:napi...@gmail.com]
Sent: Wednesday, July 22, 2009 8:00 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] filesearch not finding file
Yes, HostDir is the innermost item in my installation hierarchy. It contains
a component and an ini
ohn Ludlow
To: "General discussion for Windows Installer XML toolset." <
wix-users@lists.sourceforge.net>
Date: Wed, 22 Jul 2009 21:59:59 +0100
Subject: Re: [WiX-users] filesearch not finding file
What sets HostDir? Does HostDir point to a folder containing msi.ini
(you can check t
>So instead I'm checking for the presence of this file. If it's there, I
want
>to fail the install.
Not sure how and when HostDir property gets its value. You might want to
make it public (all uppercase and Secure set to "yes") if AppSearch happens
in the InstallExecuteSequence.
Alex
-
it's there, I want
> to fail the install.
>
> -- Forwarded message --
> From: "Wilson, Phil"
> To: General discussion for Windows Installer XML toolset. <
> wix-users@lists.sourceforge.net>
> Date: Wed, 22 Jul 2009 11:09:47 -0700
> Subjec
for Windows Installer XML toolset. <
wix-users@lists.sourceforge.net>
Date: Wed, 22 Jul 2009 11:09:47 -0700
Subject: Re: [WiX-users] filesearch not finding file
What's the goal here? Are you looking for that file, or is it just a marker
for a previous version of the product? If it was previo
What's the goal here? Are you looking for that file, or is it just a marker for
a previous version of the product? If it was previously installed with an MSI
package a component search would be more reliable - it doesn't depend on
directory locations, and it works if the user changes the install
David Bartmess wrote:
> Is there any way to get around this? Can a TOOLSDIR property be set before
> AppSearch is complete, or do I need to hard-code the path in there?
>
AppSearch, among its many weaknesses, doesn't support a way of
explicitly ordering the searches, so you can't rely on one
I found the problem. The TOOLSDIR directory is not created at the time that the
global property is being set after AppSearch.
Is there any way to get around this? Can a TOOLSDIR property be set before
AppSearch is complete, or do I need to hard-code the path in there?
Source:
. . .
From: Alex Shevchuk [mailto:shevc...@live.com]
Sent: Friday, June 05, 2009 5:28 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] FileSearch not working.
Path attribute has AnyPath type
(http://msdn.microsoft.com/en-us/library/aa367562(VS.85).aspx).
Path attribute has AnyPath type
(http://msdn.microsoft.com/en-us/library/aa367562(VS.85).aspx). It is
either actual path (or subpath) or it may contain property enclosed in
brackets. My guess is that TOOLSDIR is a property containing path where
MCT.exe is located. If that assumption is correct,
Have you checked out https://sourceforge.net/tracker/?
func=detail&atid=642714&aid=1656236&group_id=105970 yet?
One trick is to set a property with the folder first and than add a
filesearch using that property.
Best regards,
Sebastian Brand
Instyler Software - http://www.instyler.com
On Oc
22 matches
Mail list logo
