Is there anybody who had a chance to try the above, as per link: http://msdn.microsoft.com/en-us/library/aa367575(VS.85).aspx
I was just unpleasantly surprised that it appears not to work for my MSIs. For example, I had version 5.0.0.12 of one DLL installed. After issuing command line as per link above: msiexec /fvomus [path to updated .msi file] the installed DLL still remained at version 5.0.0.12, even if fresh install of the updated MSI installs expected new version 5.0.0.13. The same problem occurred not just with one DLL but with all versioned files. What can I look for in MSI log to help me debug this? When I apply small update patch via mcp then log has info about files to be patched (or no) and why, but in this case MSI log didn't tell me anything that I could parse about the reason for the files to remained untouched. ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
