In article <[EMAIL PROTECTED]>,
"Wilson, Phil" <[EMAIL PROTECTED]> writes:
> MsiInstallProduct *DOESN'T* return 0x80004005 for a missing MSI file. It retu
rns ERROR_FILE_NOT_FOUND (2) if the file isn't found and ERROR_PATH_NOT_FOUND (
3) if the path does not exist. This goes back to Richard's question, which (par
aphrased) is how the heck are you calling MsiInstallProduct?
I think the translation to E_FAIL was in his own homebrew interop
layer.
That's why I suggested using my interop layer as it doesn't substitute
any error values from what is returned from MSI. All errors turn into
exceptions with the appropriate error code.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
