Duh... I made the change to the Path attribute, but it's still not finding 
either of the files.  The log output is below.

I verified that the file exists (at least MCT.exe does, the applications.xml is 
created by the install) . The applications.xml is being checked because it 
should be created by a prior installation. At the time I ran the installer, it 
existed also.

Action 9:14:03: AppSearch. Searching for installed applications
Action start 9:14:03: AppSearch.
AppSearch: Property: MCT_INSTALLED, Signature: CheckTOOLSDIR
MSI (c) (A8:B0) [09:14:03:073]: Note: 1: 1322 2:  
MSI (c) (A8:B0) [09:14:03:073]: Note: 1: 1322 2:  
AppSearch: Property: MCT_HAS_RUN, Signature: MCT_MADE
MSI (c) (A8:B0) [09:14:03:073]: Note: 1: 1322 2:  
MSI (c) (A8:B0) [09:14:03:073]: Note: 1: 1322 2:  
MSI (c) (A8:B0) [09:14:03:073]: Note: 1: 1325 2: applications.xml 
MSI (c) (A8:B0) [09:14:03:073]: Note: 1: 1325 2: applications.xml 
AppSearch: Property: NETFRAMEWORK20, Signature: NetFramework20
MSI (c) (A8:B0) [09:14:03:073]: PROPERTY CHANGE: Adding NETFRAMEWORK20 
property. Its value is '#1'.
AppSearch: Property: NETFRAMEWORK11, Signature: NetFramework11

-----Original Message-----
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).  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, you need to add
brackets:

<DirectorySearch .. Path="[TOOLSDIR]" ...


Alex




-----Original Message-----
From: David Bartmess [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 
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 appreciated...

<Property Id="MCT_INSTALLED" Value="0">

<DirectorySearch Id="CheckTOOLSDIR" Path="TOOLSDIR" Depth="0"
AssignToProperty="yes">

<FileSearch Id="CheckMCT" Name="MCT.exe"/>

</DirectorySearch>

</Property>

<Property Id="MCT_HAS_RUN" Value="0">

<DirectorySearch Id="MCT_MADE" Path="TOOLSDIR" Depth="0"
AssignToProperty="yes">

<FileSearch Id="applications.xml" Name="applications.xml"/>

</DirectorySearch>

</Property>

Log:
AppSearch: Property: MCT_INSTALLED, Signature: CheckTOOLSDIR MSI (c) (AC:84) 
[15:32:30:023]: Note: 1: 1322 2:
MSI (c) (AC:84) [15:32:30:023]: Note: 1: 1322 2:
AppSearch: Property: MCT_HAS_RUN, Signature: MCT_MADE MSI (c) (AC:84) 
[15:32:30:023]: Note: 1: 1322 2:
MSI (c) (AC:84) [15:32:30:023]: Note: 1: 1322 2:
. . .
Property(N): MCT_INSTALLED = 0
Property(N): MCT_HAS_RUN = 0


David Bartmess

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to