Thanks for the pointers Phil!

I would just like to clarify that the root of the problem that I'm having seems 
to be in the fact that nothing gets installed, not even the policy files. I 
looked into the manifest of all of my executables, finding entries like:

<assemblyIdentity type="win32" name="Microsoft.VC90.CRT" 
version="9.0.30729.4148" processorArchitecture="x86" 
publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity></dependentAssembly></dependency><dependency><dependentAssembly><assemblyIdentity
 type="win32" name="Microsoft.VC90.MFC" version="9.0.30729.4148" 
processorArchitecture="x86"..>  

That is expected since I am indeed using #define _BIND_TO_CURRENT.

This particular user, that I was monitoring, has no higher version of MFC on 
his system. I would hope that higher version would redirect to itself, failing 
to find earlier version 9.0.30729.4148. But this would be the first time that 
any 9.x version of MFC gets installed on his system. I assume he has CRT 
because some fresh Windows 7 64 installs that I've seen come with CRT 
9.0.30729.4926, as also confirmed in this thread:
http://social.msdn.microsoft.com/Forums/en-US/vcgeneral/thread/4d710d89-de7f-4d1f-8148-0aee63bf396d

In his MSI log I see entries like:

MSI (c) (80:54) [10:50:01:362]: PROPERTY CHANGE: Adding 
WindowsFolder.30729.4148.policy_9_0_Microsoft_VC90_MFCLOC_x86.QFE property. Its 
value is 'C:\Windows\'.
Action ended 10:50:01: 
WindowsFolder.30729.4148.policy_9_0_Microsoft_VC90_MFCLOC_x86.QFE. Return value 
1.
MSI (c) (80:54) [10:50:01:362]: Doing action: 
WindowsFolder.30729.4148.policy_9_0_Microsoft_VC90_OpenMP_x86.QFE

At the end of the install there is not a single file or folder containing 
pattern *30729.4148* in his winsxs.


-----Original Message-----
From: Wilson, Phil [mailto:phil.wil...@invensys.com] 
Sent: Tuesday, May 25, 2010 12:51 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Do UFOs visit Install land?


The issues are typically:

Debug vs Release builds with different CRT requirements in the manifest (debug 
not same as release).

People using merge modules, but not the policy merge modules that redirect old 
versions of the CRT up to the newer one. That means that sometimes you get 
inconsistent policies. The VCRedists always install policy assemblies to 
redirect users to the newer versions (last time I looked anyway). 

Misleading messages. MFC says it won't load, but maybe it's really the C 
Runtime that won't load, that MFC depends on. 

The #define_BIND_TO_CURRENT... macros can make things awkward if you have 
something like the ATL security fix on your system or other updates that are 
not included in the standard redist. 

Basically it doesn't matter what MFC/CRT files are on the system when there are 
policy files redirecting you. You'd have to look at your manifest, then see 
what MFC policy files are there that might redirect you, and the same for the 
CRT. 

Phil Wilson 

-----Original Message-----
From: Tony Juricic [mailto:tjuri...@tradestation.com] 
Sent: Monday, May 24, 2010 11:36 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Do UFOs visit Install land?

Hi Phil,

Here are the missing context and details. 

The app is 32 bit. It was built with C++ redistributables version 
9.0.30729.4148. Exactly the same vcredist_x86.exe, that was installed on a 
build machine before RTM build, is run on end user's machine, before the 
application-specific MSI install starts. Hundreds of hours of testing of this 
install was done on pristine OS installs, from 32-bit and 64-bit XP SP2 OS, to 
equivalent Vista, Windows 7 and Windows Server 2008 OS.
Approximately 4000 users, using 7 OS versions, did run exactly the same setup 
executable without any problems. It is only about 2 dozen Windows 7 64-bit 
users that have either this exact, or a similar problem, with the end result 
that the main app can't find MFC DLL version 9.0.30729.4148 and reports it in 
Windows Application Event Log as a side-by-side error.

Tony

-----Original Message-----
From: Wilson, Phil [mailto:phil.wil...@invensys.com] 
Sent: Monday, May 24, 2010 2:13 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Do UFOs visit Install land?


The C++ runtimes are very specific about what they want. You didn't say what 
versions you're referring to, but there are people have installed VC++ 2008 
redist thinking it will support their VC++ 2005 app (it won't), and, for 
example, if you have built with VC++ 2008 SP1 the RTM VC++ 2008 redist won't 
help. They're almost sde by side, just to confuse things more. The app is 
32-bit, I assume, but apart from that the UFOs are just hiding the gory details 
;=)  

Phil Wilson 

-----Original Message-----
From: Tony Juricic [mailto:tjuri...@tradestation.com] 
Sent: Monday, May 24, 2010 7:39 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Do UFOs visit Install land?

The title reflects the strangeness of the problem that I am trying to solve. It 
is not WiX specific but in the broader install community there is higher chance 
that somebody may have had similar experience.
It starts with user installing vcredist_x86.exe on his Windows 7 64-bit. He is 
sharing his desktop and I see vcredist_x86.exe UI. Installation is declared 
successful and ARP also shows C++ redistributables as installed. MSI log shows 
successful install listing CRT, MFC and other Dlls as copied to Windows\winsxs 
folder on user's machine.  Yet, the application won't run because of 
side-by-side error involving missing MFC dll. Opening winsxs folder we see that 
supposedly installed libraries are nowhere to be found.
Uninstalling and installing C++ redistributables several times didn't change 
the situation.


_______________________________________________

TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) 
of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, 
FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and 
subscription company, and TradeStation Europe Limited, a United Kingdom, 
FSA-authorized introducing brokerage firm. None of these companies provides 
trading or investment advice, recommendations or endorsements of any kind. The 
information transmitted is intended only for the person or entity to which it 
is addressed and may contain confidential and/or privileged material. Any 
review, retransmission, dissemination or other use of, or taking of any action 
in reliance upon, this information by persons or entities other than the 
intended recipient is prohibited. If you received this in error, please contact 
the sender and delete the material from any computer.

------------------------------------------------------------------------------

_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to