I'm starting to get paranoid now, having been bitten so many times along the MSI journey.
Currently I link most of my applications statically to the VC runtimes, but in the case where I want to redistribute the MFC/VC runtimes, which is the best way? I've looked through the latest vcredist package, and found that the files in it weren't marked as permanent. As I only install vcredist.exe if it's product code isn't present in my custom bootstrapper, it seems to me it will only be installed with the first product I install. After that, it's on the system. That makes sense, but what happens if after you install my product, someone uninstalls vcredist.exe. Will all of my required DLL's be uninstalled out from under me if the files weren't already installed on the computer from another component? I can't see how to add a reference to a component that I didn't install. I leaned toward the vcredist method, because it makes for smaller installs, as you don't need to ship the contents to everyone, and also because the merge modules generated so many warnings. But on further investigation, it appears that the vcredist packages aren't properly signed either. The external package is signed on the new redist, but after hitting the license agreement page, you're presented with the UAC dialog, saying that: VCREDI~3.EXE from an unknown publisher wants to access your computer. That's maybe a little too scary for my users. Anthony Wieser Wieser Software Ltd ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
