Re: attaching Dlls to exe
"David Webber" <dave@musical-dot-demon-dot-co.uk> wrote in message
news:OHgrDJ5wHHA.4300@TK2MSFTNGP04.phx.gbl...
I must admit that registering DLLs is something I have never done. The
DLL's which I write (lots of them) are for use by one program only and are
installed in the program's folder.
What are the advantages of registering DLLs, and do any of them apply in
the above case?
Hi Dave... to me registering DLL's only makes sense if the DLL is a COM
object. I don't know what it means to register a DLL that isn't a COM
object.
But, if the DLL is a COM object, normally apps can't use it unless it is
registered. So my post build steps use regsvr32.exe to register the DLL so
that when I debug the app, the COM object is available.
However, you may be using Reg Free COM (which I only recently learned about
even though it's been available since XP), which lets you specify the
registration info like GUID, etc. that normally goes into the registry in
your app's manifest that consumes the COM control. This lets your app use
the COM control (if it's in the same folder as your app) even if the COM
control is not registered in the registry. Is this what you're doing?
Unless you've specified the GUID and stuff in the manifest, I don't think
just having the DLL in the same folder as your app is enough to get your app
to use it.
This is major cool because it lets apps use COM objects without having to be
an Admin to install the COM objects, plus it clears the registry, and makes
for an XCOPY deployment.
Cheers,
David