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".
lt;/DirectorySearch> </DirectorySearch>
> </DirectorySearch> </DirectorySearch> </Property>
> </Fragment>
>
> --
> John Merryweather Cooper
> Build & Install Engineer -- ESA
> Jack Henry & Associates, Inc.(r)
> Shawnee Mission, KS 6622
;
--
John Merryweather Cooper
Build & Install Engineer -- ESA
Jack Henry & Associates, Inc.(r)
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: K Peters [mailto:kpet...@otaksoft.com]
Sent: Thursday, August 29,
Hi,
I am still struggling with my FileSearch - no matter what I try,
it always pops up the "File does not exist next to MSI" message.
I have tried using "SourceDir" as well as the absolute path to where both
the MSI & the inifile reside - same negative results.
Does anyone have an idea as to wher
solution 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] FileSearch on INSTALLLOCATION, whereas INSTALLLOCATION
> is either registry entry or nes
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:
Hi,
In the WiX tutorial is a sample that does:
- reads the path to the installation directory from the registry
- checks if in that directory a specific file exists
- if yes, installs the a specific feature (docu)
What I would have wanted would have been:
- reads the path to the instal
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
hanges the install folder from
the default Program Files location.
Phil Wilson
-Original Message-
From: Eric Napier [mailto:napi...@gmail.com]
Sent: Wednesday, July 22, 2009 8:29 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] filesearch not finding file
I want to fail an insta
I want to fail an installation if a file (msi.ini) is present. My filesearch
element doesn't seem to be finding my file. I've confirmed the file is
there.
If I remove the filesearch element, the directory search finds the directory
and fails the install. However, when I include the filesearch eleme
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).
, you need to add
brackets:
mailto:david.bartm...@wallst.com]
Sent: Friday, June 05, 2009 2:49 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] FileSearch not working.
I'm trying to verify that two files exist, using a property with embedded
FileS
I'm trying to verify that two files exist, using a property with embedded
FileSearch. But this doesn't seem to be working. Each time I run it, in the log
file it lists it as "0", which is the default property value, from what I've
read and how I've got it coded below.
Any help would be apprecia
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
Hi,
I'm trying to unsinstall an app other then the one I install (by calling its
uninstall.exe).
Here is how I do this:
...
...
...
AND (!FullInstallation = 3) AND
APPUNINSTALL
...
Well, I want the custom action executed only on
All,
I install my app in C:\Program Files\Company\App 1.1 ... There is a
subdirectory Archive\ that does not get removed upon uninstallation.
How do I search for the most recent version of App and copy all the files
within App 1.1\Archive to a new directory?If someone can show me an
All,
I install my app in C:\Program Files\Company\App 1.1 ... There is a
subdirectory Archive\ that does not get removed upon uninstallation. How do I
search for the most recent version of App and copy all the files within App
1.1\Archive to a new directory?
If someone can show me an
The following FileSearch element works as expected on x86 machines but it
doesn't work on x64 machines, with 64bit SQL, even though the file version of
sqlservr.exe appears to be the same. Does FileSearch not support x64? Is
there a trick to make it work?
During my installation I am executing a C# executable program to preform an
action. Upon closing this program I would like my installer(msi) to check to
see if a file was created during this custom action. I tried determining if
the file existed using the property function with the child filesearc
31 matches
Mail list logo
