Re: Redistributing VS2008 MFC app?
Well, actually, the WinSxS and manifest concept was designed specifically to solve the DLL Hell
problem. DLL Hell was the result fo having only one version of any given file that could reside on
the machine, and when other applications replaced that one version, it broke lots of other apps. by
having "side by side" multiple versions, with each app manifested to the version it needed, DLL was
resolved. Unfortunately, because of all the confusion related to the need of manifests and the
proper way to use them, along with a few VC++ installation bugs that didn't distribute new ones
properly, we ended up with a "Manifest Hell" instead.
The SxS and manifest concept is one that could have been a wonderful solution for everyone -- if it
had been rolled out better. Unfortunately, it confused so many people (and many others were just
stubbornly resistant to the idea) that it hasn't been successful.
"David Webber" <firstname.lastname@example.org> wrote in message
"Jochen Kalmbach [MVP]" <nospam-Jochen.Kalmbach@holzma.de> wrote in message
As I said: The VC++ team has "learned" and has removed the manifest-stuff
in VS2010 ;)
In VS2010 you can just deploy the CRT/MFC DLLs with your app, without
modifying anything (xcopy-deployment).
That is WONDERFUL!
I always wondered about this "DLL Hell" which so many people were whingeing about, until manifests
dropped me right in it :-(
Author of 'Mozart the Music Processor'
For discussion/support see