Why not author the hardware checks etc in the DLL rather than have a DLL
call an executable & then set the property?
There is a way to do what you are trying to do which involves extracting
both files to a known location & then cleaning up afterwards but it
seems a bit overly complex for your requirements. If you really are
interested have a look at the solution at the end of this thread
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Quiet-Exec
ution-of-an-executable-embedded-within-the-MSI-td5191934.html


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: Paul Markey [mailto:paul_mar...@hotmail.com] 
Sent: 01 September 2010 21:59
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] (no subject)



Okay I've spent a lot of time trying to figure out my following wix
problem but I've yet to find an solution that works.
 
The original goal was to run a bat file that had already been written
right at the welcome screen that would do a hardware requirements
pre-check at the beginning of the install and exit with an appropriate
error dialog box if the conditions were not met without installing
anything.
 
At this point of the install you are unable to run a bat file because
the files haven't been transferred to the local disk yet.  So I figured
I'd convert the batch file into an exe file and store it in the binary
table and create a custom action of type 2.  So when the user clicks on
the next button from the welcome screen the exe is called from the
binary table and executed.  I managed to do this and everything looked
great but there was no way to get the exit code from the exe so I
couldn't spawn an error dialog if the hardware check failed.  
Wix only passes back a failed bat file if it's unable to properly
execute it.
 
So I figured I could write a C++ dll wrapper that would allow me to run
the exe and then set an msi property based upon the exit code of the
exe.  Setting the property was no issue however I'm unable to get the
location of the exe file that's stored in the binary table to the dll so
that it can execute the executable.
 
Essentially I can't find the executable (or have a link to it) that
enables me to run it from the dll.  Is there a solution to this issue or
the first issue of dealing with exit codes from a exe.  I haven't been
able to find a solution to either of these two items and I've spent a
fair bit of time working on this.  
I need help.                                      
------------------------------------------------------------------------
------
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