Re: [WiX-users] Custom Action Not Running In XP 32-Bit

2011-03-26 Thread Rob Mensching
I often use depends.exe if a CustomAction is failing to log anything (all
the WiX custom actions log specific errors on failure).
On Thu, Mar 24, 2011 at 8:30 AM, Liam Flanagan  wrote:

> Hello,
>
>
>
> I have a custom action function written in C that is called from a Wix MSI.
> This custom action runs successfully on Windows 7 (32-bit & 64-bit), Vista
> (32-bit & 64-bit) and Windows XP 64-bit however appears to simply not run
> on
> Windows XP 32-bit.
>
>
>
> The underlying issue here was that code within the dll for this custom
> action (not specifically code called or accessed from the entry point into
> the dll within the wix) referenced a call to the WinAPI RegDeleteKeyEx
> function which is unsupported in XP 32-bit.
>
>
>
> Now my question here is simply is there some way I could have been informed
> about why this dll wasn't loading let alone running from the install?
>
>
>
> For your information:
>
> . As this was a custom action that failed to load the installer
> continued happily without kicking up any fuss to the user
>
> . I ran the msi with /l*vx and I couldn't find anything within the
> log file that suggested the dll hadn't even been loaded, in fact you even
> get a message in the log file stating that the InstallIME (the wix) action
> ending with a return value of 1. See below an extract from the log for a
> install where the custom action failed to load:
>
>
>
> MSI (s) (2C:2C) [15:25:11:617]: Doing action: InstallIME
>
> Action 15:25:11: InstallIME.
>
> Action start 15:25:11: InstallIME.
>
> InstallIME:
>
> Action ended 15:25:11: InstallIME. Return value 1.
>
>
>
> . Just to remind you the problematic code that used RegDeleteKeyEx
> wasn't even called / referenced by InstallIME32 therefore it clearly just
> didn't want to load the dll at all
>
>
>
> In the end I managed to solve the issue through trial and error but I'm
> convinced there must be a more pragmatic (and hopefully quicker) approach,
> even if it is simply getting a warning that the custom action dll has not
> loaded.
>
>
>
> Thanks,
>
>
>
> Liam
>
>
> --
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software
> be a part of the solution? Download the Intel(R) Manageability Checker
> today! http://p.sf.net/sfu/intel-dev2devmar
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


-- 
virtually, Rob Mensching - http://RobMensching.com LLC
--
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Custom Action Not Running In XP 32-Bit

2011-03-24 Thread Liam Flanagan
Hello,

 

I have a custom action function written in C that is called from a Wix MSI.
This custom action runs successfully on Windows 7 (32-bit & 64-bit), Vista
(32-bit & 64-bit) and Windows XP 64-bit however appears to simply not run on
Windows XP 32-bit.

 

The underlying issue here was that code within the dll for this custom
action (not specifically code called or accessed from the entry point into
the dll within the wix) referenced a call to the WinAPI RegDeleteKeyEx
function which is unsupported in XP 32-bit.

 

Now my question here is simply is there some way I could have been informed
about why this dll wasn't loading let alone running from the install?

 

For your information:

. As this was a custom action that failed to load the installer
continued happily without kicking up any fuss to the user

. I ran the msi with /l*vx and I couldn't find anything within the
log file that suggested the dll hadn't even been loaded, in fact you even
get a message in the log file stating that the InstallIME (the wix) action
ending with a return value of 1. See below an extract from the log for a
install where the custom action failed to load:

 

MSI (s) (2C:2C) [15:25:11:617]: Doing action: InstallIME

Action 15:25:11: InstallIME. 

Action start 15:25:11: InstallIME.

InstallIME: 

Action ended 15:25:11: InstallIME. Return value 1.

 

. Just to remind you the problematic code that used RegDeleteKeyEx
wasn't even called / referenced by InstallIME32 therefore it clearly just
didn't want to load the dll at all

 

In the end I managed to solve the issue through trial and error but I'm
convinced there must be a more pragmatic (and hopefully quicker) approach,
even if it is simply getting a warning that the custom action dll has not
loaded.

 

Thanks,

 

Liam

--
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users