Re: [WiX-users] Bootstrapper and MsiInstallProduct [Solved]

mailto:wix-users- > [EMAIL PROTECTED] On Behalf Of Richard > Sent: Friday, January 25, 2008 1:06 AM > To: WiX Users > Subject: Re: [WiX-users] Bootstrapper and MsiInstallProduct [Solved] > > > In article > <[EMAIL PROTECTED]>, > "Wilson, Phil" <[EMAIL

Re: [WiX-users] Bootstrapper and MsiInstallProduct [Solved]

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'

Re: [WiX-users] Bootstrapper and MsiInstallProduct [Solved]

. Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Krause, Henning Sent: Thursday, January 24, 2008 2:30 AM To: Richard; WiX Users Subject: Re: [WiX-users] Bootstrapper and MsiInstallProduct [Solved] Hello, I've resolved the issue. Th

Re: [WiX-users] Bootstrapper and MsiInstallProduct [Solved]

Hello, I've resolved the issue. The problem was that when I installed another executable I had an OpenFile common dialog from which I chose that executable. This file dialog caused the current directory to be changed. I then called MsiInstallProduct with a relative path which failed because the i