Please include the wix-users list so that everyone can benefit from the conversation.
Have you placed a MessageBox/Alert at the very beginning of your code for your CA? I know this seems redundant but I've had some weird dependency errors, when I didn't have any dependencies. Another way you can check this, is to run your installer on another dev machine with the same packages installed. Additionally, I hope that this is the case, but you should never ship a debug dll/app as it will link to different dlls that will not exist on the target machines unless they have dev tools installed. So if you dll is being built as debug, build it as release and then test your installation. Nick On 6/1/06, Mateusz Bajer <[EMAIL PROTECTED]> wrote:
Hi, thanks for suggestions. Versions of MSI are the same on both machines. There are no dependencies at all, no manifests, no stuff like that. A dependency viewer which I am using shows that the dll depends only on kernel32.dll, msi.dll and user32.dll. Of course, I did such things like MessageBox just at the beginning of the function. It is not shown, but MSI log indicates that there is an error when calling my DLL (return code 3). Any other suggestions? Thanks in advance, Mateusz -----Original Message----- From: Nicholas Muguira [mailto:[EMAIL PROTECTED] Sent: Thursday, June 01, 2006 3:16 PM To: Mateusz Bajer Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Installer does not show error messages on some machines - I would check the installer versions on the target machines and see if that is causing your problem. I've run into a couple of scenarios where my dev machine had a newer version where it caused unexpected behavior on the target machine, and at least once where the newer version didn't work as expected and it worked on the target but not my dev. - After that, I would make sure that your dll has no dependencies, if it has a manifest that it is configured correctly, and that it is allowed to load. It's possible that you are linked against a debug dll and your Custom Action dll is never loaded. Put a MessageBox("Hey", MB_OK); at the top of your Custom Action to see if it is even running. Nick On 6/1/06, Mateusz Bajer <[EMAIL PROTECTED]> wrote: > > Hi, > I've been struggling with the following problem: my installer calls an > external dll by a custom action. This dll reads an xml file. I > discovered that in case of an error, the installer shows appropriate > error message box (I use the MsiProcessMessage method to inform > installer about an error), but only on the machine I develop the > installer. I tried to run it on two other laptops and there is nothing shown except the final FatalErrorDlg. > I was not sure if there is something wrong with the dll or with > installer, so I wrote a function in this dll which always returns > error code and forces MSI to log this error and show the message: and > again the result was exactly the same - just fine on my machine, but > neither log entry nor message box was shown on two other machines? > > Anybody has any idea? > Mateusz
------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
