: 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
On 30/07/2012 23:59, Chris Dahl wrote:
My question then is how can I using Wix set the merge entry to *not* try to
install the VC10 merge module if it already exists on the system? The problem
we are having is that our installer is trying to install it, but it's in use
currently by another
Thanks Bruce.
I looked at the CBS.log file to get some further information. And I
believe this is the reason why the reboot is occurring. This even happens
if I run the installation process 'As Administrator'. What are .rbf files,
and why can't they be deleted?
Thanks in advance.
MSI
And I also ran the installer in UI mode, and checked the MSI log when the
The setup must update files or services that cannot be updated while the
system is running message. This is the last line in the log file:
MSI (s) (A8:A8) [19:50:34:351]: Component:
On 31/07/2012 11:06, Chris Dahl wrote:
And I also ran the installer in UI mode, and checked the MSI log when the
The setup must update files or services that cannot be updated while the
system is running message. This is the last line in the log file:
You seem to be installing the VC90 CRT,
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
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
Thanks to Bob for pointing out that the VC10 merge module no longer installs to
the winsxs directory. Now it installs to Windows\System32.
My question then is how can I using Wix set the merge entry to *not* try to
install the VC10 merge module if it already exists on the system? The problem
That will be the default behavior. Look at the verbose log file to see why
the Windows Installer thinks it needs to install the files.
On Mon, Jul 30, 2012 at 3:59 PM, Chris Dahl chris.d...@nitropdf.com wrote:
Thanks to Bob for pointing out that the VC10 merge module no longer
installs to the
On 30-Jul-12 18:59, Chris Dahl wrote:
My question then is how can I using Wix set the merge entry to *not* try to
install the VC10 merge module if it already exists on the system?
1. Worth noting: Merge modules are a build-time concept; once merged,
they lose their identity as a
As part of our MSI installer we include the VC100_MFC and VC100_CRT merge
modules, and we expect them to be written to a SxS location in %windir%\winsxs\.
However, we've troubleshooting an issue at the moment where in the event viewer
on Windows it shows that the installer needs access to the
On 29-Jul-12 22:11, Chris Dahl wrote:
As part of our MSI installer we include the VC100_MFC and VC100_CRT merge
modules, and we expect them to be written to a SxS location in
%windir%\winsxs\.
The VC10 runtime switched back to System32; VC9 was the last to use WinSxS.
--
sig://boB
12 matches
Mail list logo
