Re: System-wide hooking, VB+ASM
- From: "Sam Hobbs" <samuel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 6 Jun 2005 14:58:54 -0700
"Simon Woods" <simonDELETECAPSjwoods@xxxxxxxxxxxx> wrote in message
news:OobPF5maFHA.2128@xxxxxxxxxxxxxxxxxxxxxxx
>
>
> Where I am is that I see a DLL as simply binary data in a particular
> form/wrapping ... whatever. Why can't that binary data be placed into a
> standard project in the same way as any other thunk and be used/invoked
> (however that would be done) for system-wide hooking?
I apologize if I am interpreting this out of context, but I think I can
answer in a useful manner.
Another way of describing a DLL is as a collection of functions that can be
related but are not required to be realted to be in a DLL. I think you know
that but I am not sure.
I think the problem is the VB runtime. It is very common for higher-level
languages such as VB to have a runtime environment that must be initialized
somehow. The VB runtime environment is not a problem when an ActiveX control
is used by an applicaiton (a process) that does not use VB since apparently
VB builds into the ActiveX DLL code to initialize the runtime. When the DLL
is used in an application without the ActiveX being used and without VB
being used by that application, then it is likely that the runtime does not
get initialized. That is my guess, but it seems likely to me that it is a
problem that will prevent use of a DLL created by VB as a system-wide hook
DLL.
.
- Follow-Ups:
- Re: System-wide hooking, VB+ASM
- From: Jim Carlock
- Re: System-wide hooking, VB+ASM
- From: Simon Woods
- Re: System-wide hooking, VB+ASM
- References:
- Re: System-wide hooking, VB+ASM
- From: TC
- Re: System-wide hooking, VB+ASM
- From: Simon Woods
- Re: System-wide hooking, VB+ASM
- Prev by Date: Re: System-wide hooking, VB+ASM
- Next by Date: Re: Using Visual Basic to Write System-Wide Hooks
- Previous by thread: Re: System-wide hooking, VB+ASM
- Next by thread: Re: System-wide hooking, VB+ASM
- Index(es):
Relevant Pages
|