Re: Resolving DLL import to actual DLL using the executables manifest
- From: "Skywing [MVP]" <skywing_NO_SPAM_@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 14 Mar 2007 00:22:45 -0400
Imports won't be resolved until after the first thread is resumed in that case.
As far as what the OP was requesting, I think that you need to use the ActCtx (activation context) APIs to wrap calls to something like, say, LoadLibrary in order to load as if the module were referenced by a particular manifest. My experience with SxS is fairly limited, however.
--
Ken Johnson (Skywing)
Windows SDK MVP
http://www.nynaeve.net
"Gary Chanson" <gchanson@xxxxxxxxxxxxxxxx> wrote in message news:eABVkDBZHHA.4616@xxxxxxxxxxxxxxxxxxxxxxx
"Martin Slater" <mslater@xxxxxxxxxxxxxxx> wrote in message
news:45f3e80e$0$32429$c3e8da3@xxxxxxxxxxxxxxxxxxxx
Martin Slater wrote:
> Hi there,
>
> Can anyone point me to a simple way to resolve a DLL entry in the PE
> import table to an actual file one the filesystem taking into account
> the manifest and installed side by side assemblies without having to
> manually pass the windows winsxs directory?
I came across a possible solution (I thought) using EnumProcessModules,
code listing is at the end but this doesn't work and only returns
ERROR_PARTIAL_COPY. Anyone got any ideas of why this is so? When
creating the process suspended is the thread suspended before or after
DLL imports have been process and resolved?
Unless my memory is playing tricks on me, I'm pretty sure it's after
imports have been resolved and just before the entry point of the program is
called.
--
- Gary Chanson (Windows SDK MVP)
- Abolish Public Schools
.
- Follow-Ups:
- Re: Resolving DLL import to actual DLL using the executables manifest
- From: Martin Slater
- Re: Resolving DLL import to actual DLL using the executables manifest
- References:
- Resolving DLL import to actual DLL using the executables manifest
- From: Martin Slater
- Re: Resolving DLL import to actual DLL using the executables manifest
- From: Martin Slater
- Re: Resolving DLL import to actual DLL using the executables manifest
- From: Gary Chanson
- Resolving DLL import to actual DLL using the executables manifest
- Prev by Date: Re: problem in creating a new process(intereactive) in session 1 from session 0 in Vista
- Next by Date: Re: Invalidating the file cache
- Previous by thread: Re: Resolving DLL import to actual DLL using the executables manifest
- Next by thread: Re: Resolving DLL import to actual DLL using the executables manifest
- Index(es):
Relevant Pages
|