In article
<682e56117f9ba0419d5247669e3f742d836478e...@invsfoxxchmbx02.corp.com>,
"Wilson, Phil" <[email protected]> writes:
> Richard would have to look at his code's manifest and see what
> redirection exists on the machine for that particular runtime Dll.
Hmm.... OK, this is giving me a clue where to look.
I don't have an application manifest that I'm specifying explicitly.
I'm getting whatever Visual Studio 2008 SP 1 with ATL Security Update
decides to generate. Inside the generated exe.intermediate.manifest
file, I find this:
<dependency>
<dependentAssembly>
<assemblyIdentity type='win32' name='Microsoft.VC90.CRT'
version='9.0.21022.8' processorArchitecture='x86'
publicKeyToken='1fc8b3b9a1e18e3b' />
</dependentAssembly>
</dependency>
That tells me that the automatically generated manifest is pointing to
the *old* CRT, which is why I need the policy file to redirect from
the old one to the one in the patched redist.
Now I can explicitly configure the compiler manifest tool to use the
right options, but geez, it feels like a bug in VS.NET here because
they've stopped making the old runtime redist available, but the
compiler is generating references to that old runtime by default.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>
Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
