Blair Hall wrote: > > > I get your point that the first manifest I provided is not specific to > the DLL, but the second (embedded in the DLL) manifest that I posted > seems to identify a particular version of msvcr90.dll. Sadly, Windows > does not worry about matching the version of msvcr90.dll: it just > loads the first one it finds with the correct name. So what is the > embedded manifest in the DLL really there for?
There's a "greater than or equal to" aspect to this as well. There is a way for a package to say "I can also be loaded when apps ask for earlier releases". There can also be a conflict between the needs of an EXE and the needs of a DLL. If the EXE has a manifest that requests a certain version of the CRT, then a DLL can't really override it. You have an ugly, icky problem, and I'm not quite sure what to advise you. The traces you are showing don't necessarily match with what I would have expected. I don't understand why the Intel version of the CRT is getting chosen, and I don't understand why it's failing to link up with it again later. -- Tim Roberts, t...@probo.com Providenza & Boekelheide, Inc. _______________________________________________ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32
