In article <[EMAIL PROTECTED]>,
"dB." <[EMAIL PROTECTED]> writes:
> We're entering a philosophical debate of where custom actions start and
> end.
As far as the code goes, custom actions start at their entry point and
end when they return to the Windows Installer engine.
Unit testing them this way is very easy.
Unit testing a custom action doesn't mean you don't have to test your
install, but it will catch stupid "fat finger" programming mistakes
while coding the custom action more quickly than other methods.
--
"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 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
