hi all, I'm trying to do a system verification step as part of my install, but I've encountered a small problem with the standard custom action dll solution. I've created a CustomActions.dll to contain a isValidSystem call. unfortunately, the algorithm to validate the system is inside yet another dll (tools.dll) that I must load.
My initial knee-jerk idea was to include tools.dll as part of the installation and just fetch INSTALLDIR inside CustomActions.dll, but of course that wont work since I can't actually install the application to determine if I should install the application :) I tried including tools.dll as a binary key, but of course msi places it in the windows temp directory under some other name, and I can't access that, unless there is some way to find out the path given the binary key ID? thanks Oren ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
