During install:
ProcessComponents action lists
1: {F393E0C2-E3B5-4CD1-BD6A-8547DDEC1AE3} 2:
{BA9B764A-0DE0-11D5-A548-0090278A1BB8} 3: C:\WINDOWS\system32\mfc70u.dll
1: {F393E0C2-E3B5-4CD1-BD6A-8547DDEC1AE3} 2:
{BA9B7647-0DE0-11D5-A548-0090278A1BB8} 3: C:\WINDOWS\system32\mfc70.dll
1: {F393E0C2-E3B5-4CD1-BD6A-8547DDEC1AE3} 2:
{3AC4AA25-A28A-4F09-826A-30CA0A620F35} 3: C:\WINDOWS\system32\mfc71u.dll
1: {F393E0C2-E3B5-4CD1-BD6A-8547DDEC1AE3} 2:
{F607CA48-C332-4029-AF8A-39BDF6912CD4} 3: C:\WINDOWS\system32\mfc71.dll
InstallFiles action lists
InstallFiles: File: mfc70.dll, Directory: C:\WINDOWS\system32\, Size: 974848
InstallFiles: File: mfc70u.dll, Directory: C:\WINDOWS\system32\, Size: 964608
During repair:
InstallValidate action lists
Info 1603. The file C:\WINDOWS\system32\mfc71u.dll is being held in use by the
following process: Name: explorer, Id: 1312, Window Title: '(not determined
yet)'. Close that application and retry.
ProcessComponents action lists
1: {F393E0C2-E3B5-4CD1-BD6A-8547DDEC1AE3} 2:
{BA9B764A-0DE0-11D5-A548-0090278A1BB8} 3: C:\WINDOWS\system32\mfc70u.dll
1: {F393E0C2-E3B5-4CD1-BD6A-8547DDEC1AE3} 2:
{BA9B7647-0DE0-11D5-A548-0090278A1BB8} 3: C:\WINDOWS\system32\mfc70.dll
1: {F393E0C2-E3B5-4CD1-BD6A-8547DDEC1AE3} 2:
{3AC4AA25-A28A-4F09-826A-30CA0A620F35} 3: C:\WINDOWS\system32\mfc71u.dll
1: {F393E0C2-E3B5-4CD1-BD6A-8547DDEC1AE3} 2:
{F607CA48-C332-4029-AF8A-39BDF6912CD4} 3: C:\WINDOWS\system32\mfc71.dll
InstallFiles action lists
InstallFiles: File: mfc70.dll, Directory: C:\WINDOWS\system32\, Size: 974848
InstallFiles: File: mfc70u.dll, Directory: C:\WINDOWS\system32\, Size: 964608
InstallFiles: File: mfc71.dll, Directory: C:\WINDOWS\system32\, Size: 1060864
InstallFiles: File: mfc71u.dll, Directory: C:\WINDOWS\system32\, Size: 1053184
Info 1603. The file C:\WINDOWS\system32\mfc71u.dll is being held in use. Close
that application and retry.
MSI (s) (F4:B4) [15:28:07:752]: Product: DataCaptor Interface Server. The file
C:\WINDOWS\system32\mfc71u.dll is being held in use by the following process
Name: explorer , Id 1312.
Now that looks like during install, mfc71u.dll isn't installed (already
present) but an install is attempted during repair under C:\WINDOWS\system32
folder.
Thx,
Dacian
----- Original Message ----
From: "Wilson, Phil" <[EMAIL PROTECTED]>
To: wix-users@lists.sourceforge.net
Sent: Wednesday, November 28, 2007 7:35:18 PM
Subject: Re: [WiX-users] Conditional installation of merge modules
<!--
_filtered {font-family:"Cambria Math";panose-1:2 4 5 3 5 4 6 3 2 4;}
_filtered {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}
_filtered {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;font-family:"Times
New Roman", "serif";}
a:link, span.MsoHyperlink
{color:blue;text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
p.msochpdefault, li.msochpdefault, div.msochpdefault
{margin-right:0in;margin-left:0in;font-size:10.0pt;font-family:"Times
New Roman", "serif";}
span.emailstyle17
{font-family:"Tahoma",
"sans-serif";color:windowtext;font-weight:normal;font-style:normal;text-decoration:none
none;}
span.EmailStyle19
{font-family:"Tahoma",
"sans-serif";color:windowtext;font-weight:normal;font-style:normal;text-decoration:none
none;}
.MsoChpDefault
{font-size:10.0pt;}
_filtered {margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{}
-->
Keeping
Wix users on the list…
It’s
not clear to my why the 7.1 Dlls would be in use by Explorer unless you are
installing them into a folder where Explorer is using them from, so you’ll
have to explain exactly where they are installed to. I don’t know what
your default is because the 71 modules can be directed most places. You don’t
have to use Orca to make them go into your app folder. The module retargetable
folder can be set to your app folder.
The
VS 2005 merge modules are completely different, and have a different install
paradigm. They are installed into the systems SxS folder and if you
include (say) the VC80 merge module the corresponding policy merge module is
also included. The VS runtime executable does things differently, but the
end result is the same – a manifest that redirects clients to the current
installed version.
Phil
Wilson
From: fiordean dacian
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 28, 2007 6:26 AM
To: Wilson, Phil
Subject: Re: [WiX-users] Conditional installation of merge modules
Do you mean installing my app
under System folder? Nope.
As for the merge modules, they are installed into their default folder. If I
have to install the 71 dlls into my app's folder, I need to modify them by hand
using Orca, right?
Actually MFC71 wasn't a typo, actually I need VC2003 stuff. I just mentioned
VC2005 runtime since I saw on that blog a discussion about I don't know what
policy_*.msm thing which btw isn't included with the VC2005 runtime. So forget
that...
Me either I don't know why this is happenning when repair. I was expecting
those msm's not to install each time, but rather when not present. It looks
like they are getting installed no matter. So that's why I was wondering if
it's possible to condition their installation in Wix.
Thanks,
Dacian
----- Original Message ----
From: "Wilson, Phil" <[EMAIL PROTECTED]>
To: wix-users@lists.sourceforge.net
Sent: Tuesday, November 27, 2007 7:40:53 PM
Subject: Re: [WiX-users] Conditional installation of merge modules
Are
you installing into the System folder? The 71 Dlls can be side by side, so you
can install them into your application folder. Visual Studio 2005 support
Dlls are SxS in the WinSxS folder - they’re installed differently.
Was MFC71 a typo? That’s the Visual Studio 2003 MFC support, but
elsewhere you’re referring to 2005. I’m not sure what
you’re getting at with that “in case of a repair” –
this is just at install time, right?
Phil
Wilson
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of fiordean
dacian
Sent: Tuesday, November 27, 2007 7:07 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Conditional installation of merge modules
Hi,
I'm installing MFC71, CRT and STL merge modules together with my product. The
problem I'm having is Windows Installer asks me to reboot at the end of the
installation in case of a repair since some of those modules are held in use by
Windows Explorer. At the installation, I don't have this problem. I assume is
due to the way those merge modules are made. Is there a way to avoid this?
I'm reading through blogs around Internet about policy_* merge modules (I don't
really understand why do I need all those):
http://msdn.technetweb3.orcsweb.com/astebner/archive/2007/02/13/building-an-msi-using-wix-v3-0-that-includes-the-vc-8-0-runtime-merge-modules.aspx
I downloaded VC 2005 SP1 redistributable package from Microsoft but it doesn't
install anything of that type (ie policy_* merge module files).
http://www.microsoft.com/downloads/details.aspx?familyid=200B2FD9-AE1A-4A14-984D-389C36F85647&displaylang=en
Any thoughts?
Thanks,
Dacian
Be a better pen pal. Text or chat with friends inside Yahoo!
Mail. See how.
Get easy, one-click access to your favorites. Make Yahoo!
your homepage.
____________________________________________________________________________________
Be a better sports nut! Let your teams follow you
with Yahoo Mobile. Try it now.
http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ-------------------------------------------------------------------------
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
