How are you getting CheckCPU.exe onto the target system? You may want to
change your Custom Action to a Type 2 rather than a Type 50 as it
appears you're trying to do if your supplying the CheckCPU.exe
application inside your package. Custom Action types are listed at
http://msdn.microsoft.com/en-us/library/aa372048.aspx

Palbinder Sandher 
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the <Virtual Environment>**
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer

-----Original Message-----
From: Noran [mailto:mat...@gmx.de] 
Sent: 08 September 2010 09:42
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Msi launch file too late


Hi @ all,
i've wrote an .msi-installer which runs an external .exe this App
creates a .txt file in a Folder. after that the msi should check what
for a .txt was created and installs the right files. The Problem is even
though i set the Sequence of the Custom Action at "Before = 'AppSearch'
the msi checks first which .txt is created and then runs the .exe so it
dont finds any .txt-file and installs the wrong files.

here are some Code-Snippets:

 <CustomAction Id='LaunchFile' Property='CPUCHECKFILE' ExeCommand=''
Return='asyncWait' />

.....

<Property Id='CPUCHECKFILE'>
      <DirectorySearch Path='[CURRENTDIRECTORY]' Depth='0' Id='Current'>
        <FileSearch Id='CPU' Name='CheckCPU.exe'/>
      </DirectorySearch>
    </Property>
    
    <Property Id="STANDARD">
      <DirectorySearch Id="Standard" Path='[PersonalFolder]' Depth="0">
        <FileSearch Id="CheckFileStandard" Name="Standard.txt" />
      </DirectorySearch>
    </Property>

    <Property Id="SSE2">
      <DirectorySearch Id="Sse2" Path='[PersonalFolder]' Depth="0">
        <FileSearch Id="CheckFileSse2" Name="SSE2.txt" />
      </DirectorySearch>
    </Property>

    <Property Id="SSE3">
      <DirectorySearch Id="Sse3" Path='[PersonalFolder]' Depth="0">
        <FileSearch Id="CheckFileSse3" Name="SSE3.txt" />
      </DirectorySearch>
    </Property>

    <Property Id="SSSE3">
      <DirectorySearch Id="Ssse3" Path='[PersonalFolder]' Depth="0">
        <FileSearch Id="CheckFileSsse3" Name="SSSE3.txt" />
      </DirectorySearch>
    </Property>

    <Property Id="SSSE3A">
      <DirectorySearch Id="Ssse3a" Path='[PersonalFolder]' Depth="0">
        <FileSearch Id="CheckFileSsse3a" Name="SSSE3Atom.txt" />
      </DirectorySearch>
    </Property>

    <Property Id="SSE4">
      <DirectorySearch Id="Sse4" Path='[PersonalFolder]' Depth="0">
        <FileSearch Id="CheckFileSse4" Name="SSE4.txt" />
      </DirectorySearch>
    </Property>

<Directory Id='TARGETDIR' Name='SourceDir'>
      <Directory Id='SystemFolder' Name='INSTALLDIR'>
        
        <Component Id="MainDlls"
Guid="85180B23-7B34-4D3F-962B-27E2CD70C6ED"
>

...

        </Component>

      </Directory>
    </Directory>

 <InstallExecuteSequence>
      <Custom Action='LaunchFile' Before='AppSearch'>NOT
Installed</Custom>
    </InstallExecuteSequence>
    
    <Feature Id='Core' Level='1' >
      <ComponentRef Id='MainDlls' />
    </Feature>

    <Feature Id='Unknown' Level ='1'>
      <ComponentRef Id='Standard' />
      <Condition Level='0'>NOT STANDARD</Condition>
    </Feature>

    <Feature Id='SSE2' Level ='1'>
      <ComponentRef Id='SSE2' />
      <Condition Level='0'>NOT SSE2</Condition>
    </Feature>

    <Feature Id='SSE3' Level ='1'>
      <ComponentRef Id='SSE3' />
      <Condition Level='0'>NOT SSE3</Condition>
    </Feature>

    <Feature Id='SSSE3' Level ='1'>
      <ComponentRef Id='SSSE3' />
      <Condition Level='0'>NOT SSSE3</Condition>
    </Feature>

    <Feature Id='SSSE3Atom' Level ='1'>
      <ComponentRef Id='SSSE3A' />
      <Condition Level='0'>NOT SSSE3Atom</Condition>
    </Feature>

    <Feature Id='SSE4' Level ='1'>
      <ComponentRef Id='SSE4' />
      <Condition Level='0'>NOT SSE4</Condition>
    </Feature>

Has anyone a guess why the Installer checks first the files and then
runs the .exe?

Thankfully Noran
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Msi-launch
-file-too-late-tp5509690p5509690.html
Sent from the wix-users mailing list archive at Nabble.com.

------------------------------------------------------------------------
------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to