I am using VB6 and I was wondering if there is a way that I can make my .EXE use a .DLL without having any need to run regsvr32 to register the .DLL and things like that.

Why can't .DLLs be as uncomplicated as .EXE with .EXE everything is heaven ... its just in those situations where I need to make a .DLL help my .EXE where everything gets to feel not so good because I have to register it first.

The process becomes more and more painful the more times you need to edit the .DLL because then you have to unregister and then register again etc.

When I deploy an .EXE everything goes smoothly but deploying an .EXE that depends on a .DLL is often a pain because I need to have the user run regsvr32 just to have the .DLL work ... its just a small department and just a small program but there are red tapes that
slows down the process of implementing things with .DLL especially when it changes time and again because when that happens then I need to call up the head office again for registration permissions and things like that which of course never happens when I am just deploying an EXE.

If only I had admistrative permissions on all the machines .. but that is of course a perfect world and in the absence of that perfect world I guess the next best thing is to just have the ability to use a .DLL without having any need to register it... so is there a way to do it?

All suggestions welcome and thank you so much for all the kind help you can give.

Gratefully,
Matt

Hi
You cannot use a COM DLL without it being registered. Registration is how windows gets told what to do when you use the reference in your project.
For deployment, use one of the many installatino packages that are floating around, or at worst case, use PAckage and Deployement wizard.
Recompiliing DLLS is a pain, and results in DLL-hell. I suggest you read up on compatibility settings before you start deploying your dll around the world
.NET does allow for deployment without registered, so that may be the way forward for you (vb.net express is free)

____________________________
Build it better, faster, quicker, easier.. then fix it (non-offical MS mission statement)