Register/Unregister DLL and Binary Compatible Q's

[jeffhanson2000]

I apologize if these questions have been asked before. I searched the forums and could not find what I was looking for.

I have a program that is going to use an .exe that calls an activeX .dll. Both the .dll and the .exe were created in VB6. Right now, on my test box, I have the .exe shell to regsvr32.exe to register the .dll when the program starts, and unregister it when it ends.

Is there any disadvantage to doing it this way?

Am I filling up the registry with junk keys each time I register and unregister the .dll?

Also, do I have to use binary compatibility mode when I compile the .dll if I plan to make internal changes to the functions in future releases? By internal, I mean that I would not affect any public interfaces, just how the 'guts' of the functions work.

Thanks in advance for your help.

JH

[Edneeis]

If you register and unregister the dll within your application then that kind of defeats the part of the purpose of using the dll. Usually a dll is used to share functions among mulitple applications but since you unregister it then it wont be available to other applications unless they do the same. Why have you choosen to do this? Yes use binary compatibility.

[jeffhanson2000]

The only reason I was having the .exe register and unregister the .dll was so that it would be easy to swap out the .dll with a new version, just by making sure that the program isn't running, and copying the .dll over the old one. Am I mistaken?

Also, here's one more question. Is there any way to make the DLL so that it only works with approved programs? I mean, I guess I could write an authentication routine that checks for a password/key that is passed by the executable, but I was wondering if there was any built-in functionality.

Thanks again!

JH

[abhijit]

to do this, you could try using a class module within an exe.

rgds,
abhijit

[Edneeis]

As long as backward compatibility exists then you can just replace the dll without needing to re-register it or if new things are added then re-registering the newer one once when it is installed will still keep applications that used the old version working. If this the only application that uses the dll then you may want to follow abhijit's advice and move your classes into the exe. That would solve both of your problems.

[jeffhanson2000]

Excellent. Thank you for your help!