Hey Bruce, Thought I'd let you know that I solved this by removing the VC10 merge modules from our WiX project. The VC90 ones weren't causing a problem, however it was the other processes on the machine that had a hold on the shared files in System32 that caused the problem.
Seems Windows Installer wasn't properly checking to see if the file already existed either (or we were including a more recent version). - Chris. -----Original Message----- From: Bruce Cran [mailto:br...@cran.org.uk] Sent: Tuesday, 31 July 2012 8:26 PM To: Chris Dahl Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] SxS MFC merge module needs to write to System32. Why? On 31/07/2012 11:13, Chris Dahl wrote: > We have both as requirements for our application (due to a 3rd party > library that uses VC90, and our application that uses VC10). > > The VC90 files are installed to a SxS directory though, so how could > another application have a hold on them? And, looking at the log file > does the fact that the _RemoveFilePath entry is missing after the 'TypeLib' > line provide any clues? What does _RemoveFilePath do? Apparently there were bugs on XP with SxS installations - see the thread http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Unnecessary-reboot-when-repairing-an-install-on-Win-XP-td7579092.html where Rob said: "IIRC, there were bugs in WinSxS on Windows XP that did not handle replacing files in use well causing more reboots than necessary. Yay, Fusion!" -- Bruce Cran ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
