I'm packaging shared components in my MSI. These components (like COMDLG32.OCX
or MSCOMCTL.OCX) are installed into %system32%. However, I've got an issue
with the files not upgrading properly. I always want to have the newest
version of the shared component on the machine. As per my last question
("Concurrent versions?"), we're not using an upgrade path, but rather separate
Product/@Id's entirely.
If "version 5.0" of my software installs shared component 1.0.0.3, and "version
6.0" installs 1.0.5.0, how can I make sure that 1.0.5.0 is the version
installed regardless of the actual installation order of my software?
Thanks,
-Bryan
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
