Re: Accessing a DLL without registering it

Yes, you can bypass the COM loader and load COM objects directly which
eliminates the need for the registry information. The best source for
VB relevant info on the subject and examples is Matt Curland's
Advanced VB6 book.

HTH,
Bryan
_________________________________________________________
Bryan Stafford "Don't need no more lies"
New Vision Software - Neil Young -
www.mvps.org/vbvision Living With War : The Restless Consumer
alpineDon'tSpam@xxxxxxxx


On Mon, 5 Feb 2007 13:15:54 -0500, "Thomas Malia"
<tommalia@xxxxxxxxxxxxxxxx> wrote:

I did some quick scans of the Google search results, but they all seem to
talk about how to use COM objects in .NET programs without haveing to
register the COM libarary... In my case, both the DLL and the EXE are "Real
VB" ;-) VB6 not VB .NET... can the same thing be done in my VB6
application? If so, how?


"Chris Dunaway" <dunawayc@xxxxxxxxx> wrote in message
news:1170698591.323366.275470@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Feb 5, 10:43 am, "Thomas Malia" <tomma...@xxxxxxxxxxxxxxxx> wrote:
Hey folks,

I've written a custom DLL that I'm using within several new EXE's. For
distribution of these programs, I'd really rather NOT require any setup
process to need to be run for each workstation that the program might be
run
from. I'd rather be able to install the EXE and the DLL to a shared
directory on a server and then just let people directly launch the program
from the share without having to run any setup processes.

I had thought that actually registration of a DLL was only necessary if
the
DLL could not be found in the directory where the program was running
from.
However, so far I have not been able to get my applications to run without
explicitly registering the DLL (using Regsrv32.exe).

Is this an absolute requirement? Isn't there some way to create a
reference
to a DLL in an EXE that will first try to find the necessary DLL in the
search path of the application and IF it doesn't find it there, then look
in
the registry? I'm sure this is my naiveté about using DLL that's the
problem here. there most be something that can be done that I'm just not
familiar with.

Thanks in advance for any help,

Tom Malia

Do a google search for "Registration Free COM". There are a number of
articles that might help you.

Chris


.

Relevant Pages

  • Problem with performance of IDE devices
    ... index 0, dll tcpstk.dll, context 0x3f8a5c9 ... 0x801abbe8: FSREG: Mounted ROM portion of boot registry ... 0x8014abcc: FSREG: Invalid HKEY 0x00000000 ...
    (microsoft.public.windowsce.platbuilder)
  • Re: secure32.exe
    ... > kind of search could be used - I tried to search files that had the text ... Exe can register this dll as Winlogon ... or as extension in AppInit_Dlls registry key - this allows dll to ...
    (microsoft.public.security.virus)
  • Re: Using same interfaces for in-proc vs. out-proc
    ... I forgot to mention that when I compile the DLL after removing the TYPELIB ... and REGISTRY entries in the RC file I still get this message: ... for the COM part is in the same project as the rest of the EXE code. ...
    (microsoft.public.vc.atl)
  • Re: Transferring programmes from one partition to another
    ... the same dll location. ... If the exe file is moved, the association is broken and is not ... The dll may look to the registry but since the exe and ... of registry entries involed, you could in theory anyway, update the registry ...
    (microsoft.public.windowsxp.general)
  • Re: COM beginner - 2 apps using the same instance of a component.
    ... >> a DLL). ... > an in-proc dll server is because that is how it is used most of the time, ... > I realise I could make an out of proc server exe project and just make it ... > I would prefer not to touch the registry for this project, ...
    (microsoft.public.win32.programmer.ole)
Loading