|
-
February 9th, 2000, 01:22 AM
#1
effect of chaged DLLs
Hi,
I have developed some VB Components. Each project module has referece to other module's DLL. So when i change the DLL of one module obvisouly the other modules' DLLs which 'refer' this DLL have to be changed. What is the exact procedure to do this. Should i unregister the old DLLs and delete them..or
just create another DLL and use it ??
-
February 9th, 2000, 02:01 AM
#2
Re: effect of chaged DLLs
In my opinion, don't register the DLL's untill you have base lined your dll libraray. What I do is create reference to the required DLL from Project->Reference->Browse to the location of your dll. Or just copy the Dlls and Library to your working directory(Which is more efficient since when you have changed the DLL's then you can again replace the old dll with a new one).
HTH.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|