Hi Ari,
Thanks for tip re static link & explaining InstallExecuteSequence. Im not
really concerned though about the custom action (launch app after installation
checkbox). I only mentioned it to reference the error message 2896 in the log
in case someone suggested it. The problem is, my installer works fine using
VCRedist.exe (including the custom action) but not with merge modules - wont
launch at all, custom action or no custom action. I thought merge modules &
vcredist are the exact same thing so concluded therefore Im not configuring the
merge modules properly?
thanks,
-----Original Message-----
Where is your launchapplication custom action scheduled in the
InstallExecuteSequence?
I think that the VC redists won't actually get installed to the SxS folder
until after InstallFinalize, so if your action runs before then, the app
won't find the VC dlls and you'll get the error message you're seeing below.
I think that the answer is to launch your application after InstallFinalize.
You lose the ability to fail the install and rollback if your app fails to
launch, but maybe that's acceptable. You could also statically link the app
with the CRT & MFC and then the dlls aren't necessary.
If your CA is already scheduled after InstallFinalize, then I wasn't much
help :)
-Ari
_________________________________________________________________
Windows Live Messenger: Happy 10-Year Anniversary—get free winks and emoticons.
http://clk.atdmt.com/UKM/go/157562755/direct/01/
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
