Re: New Version of MFC for VC2005?

From:

"David Ching" <dc@remove-this.dcsoft.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Wed, 12 Nov 2008 07:07:54 -0800

Message-ID:

<B7157A49-C228-4E01-AFB2-6A1F0C1401BB@microsoft.com>

"Anthony Wieser" <newsgroups-sansspam@wieser-software.com> wrote in message
news:uIXdlPKRJHA.4916@TK2MSFTNGP06.phx.gbl...

It appears that SQL Server 2008 installs a new side-by-side mfc version:
8.0.50727.1833

The one included with SP1 was
8.0.50727.767

Trouble is my application now crashes when that one is loaded with a
Unicode release build.

How can I set up a manifest that insists on loading the one I distributed
with my application.

I tried setting up a manifest that said:
</dependency>
<dependency>
   <dependentAssembly>
     <assemblyIdentity type='win32' name='Microsoft.VC80.CRT'
         version='8.0.50727.762' processorArchitecture='x86'
         publicKeyToken='1fc8b3b9a1e18e3b'/>
   </dependentAssembly>
</dependency>
<dependency>
   <dependentAssembly>
     <assemblyIdentity type='win32' name='Microsoft.VC80.MFC'
         version='8.0.50727.762' processorArchitecture='x86'
         publicKeyToken='1fc8b3b9a1e18e3b'/>
   </dependentAssembly>
</dependency>

(It took me ages to realize the publicKeyToken is in the folder name on in
the C:\windows\sxs folder)

But when the program loads, it still is bound to 1833.

See
http://blog.kalmbach-software.de/2008/05/03/howto-deploy-vc2008-apps-without-installing-vcredist_x86exe/
which advises removing publicKeyToken.

Also, in addition to your own manifest, you need to make sure the manifests
for the CRT and MFC are put into your project folder.

-- David