Results 1 to 9 of 9
  1. #1
    Platinum Lounger
    Join Date
    Feb 2001
    Location
    Yilgarn region of Toronto, Ontario
    Posts
    5,453
    Thanks
    0
    Thanked 0 Times in 0 Posts

    What are the pros and cons of registering ANY DLL

    A typical use of the regsvr32 program is to bring a pre-compiled DLL into the fold, as this example from the Microsoft Knowledge Base shows: "regsvr32 c:windowssystemddeml.dll".


    Before I go and wreck what's left of my system with a foolhardy experiment, what are the pros and cons of registering ANY DLL?


    I would imagine that if I located every DLL on my 40G of disk storage and registered the same, my next re-boot of Win95 might not complete before Microsoft announced the launch of Windows ZZ, so I'm not thinking of that. Not immediately.

    I'm thinking of a DLL that comes with a neat and dandy stand-alone application such as RealPlayer or Acrobat Reader.

    If I were to register, say, all the DLLs with Acrobat, might I be in a position to make calls to that DLL from any VBA appliaction, thereby greatly extending the power of my efforts? Being able to recognise a file type and then use the DLL to obtain information about the file type by calling functions in the associated DLL might be useful.


    In the limit, if I did register every (shudder) DLL on my system, presumably I could spend a pleasant long-weekend examining what's available through VBA, documenting it, and, perhaps, retoring my System Registry as my last act.

  2. #2
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: What are the pros and cons of registering ANY DLL

    Most of the dlls that come with Windows or with applications get registered as part of the installation process. That's why the apps run properly.

    You normally only need to "hand" register one when something went wrong in the installation or if you load a stand-alone dll, such as one you create yourself. Oh, yes, or if one got stepped on by another installation and you have to copy it from the original disk.
    Charlotte

  3. #3
    Gold Lounger
    Join Date
    Dec 2000
    Location
    Hollywood (sorta), California, USA
    Posts
    2,759
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: What are the pros and cons of registering ANY DLL

    Say no more. There's nothing else to say...
    Kevin <IMG SRC=http://www.wopr.com/w3tuserpics/Kevin_sig.gif alt="Keep the change, ya filthy animal...">
    <img src=/w3timages/blackline.gif width=33% height=2><img src=/w3timages/redline.gif width=33% height=2><img src=/w3timages/blackline.gif width=33% height=2>

  4. #4
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: What are the pros and cons of registering ANY DLL

    Well, yes, actually there is. If you want access to the dll's objects and properties for programming purposes, set a reference to it in your application.
    Charlotte

  5. #5
    Platinum Lounger
    Join Date
    Feb 2001
    Location
    Yilgarn region of Toronto, Ontario
    Posts
    5,453
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: What are the pros and cons of registering ANY DLL

    > There's nothing else to say

    You know how I hate to disageree, but "Yes there is".

    Charlotte, having made the excellent point that most DLLs will have been automatically registered during the installation process, there remain those DLL's that are not explicitly registered.

    What advantages are there to registering any one of them? Am I not going to be surprised, from time to time, by access to aspects of a DLL to which I was not previously aware?

  6. #6
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: What are the pros and cons of registering ANY DLL

    How long is a piece of string (or a thread like this one)? If you ask rhetorical questions, don't be surprised by a lack of cogent answers. <img src=/S/shrug.gif border=0 alt=shrug width=39 height=15>
    Charlotte

  7. #7
    New Lounger
    Join Date
    Sep 2005
    Location
    United Kingdom
    Posts
    3
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: What are the pros and cons of registering ANY DLL

    Only DLLs that provide COM interfaces need to be registered. Registration provides a link in the registry between the object's name and the DLL so that when you try to create a particular object Windows knows which DLL to run.
    Many DLLs simply contain a set of C/C++ functions that other C/C++ programs call directly (the Windows API is implemented in this way). Many of these are private to the app that installed them. Registering a non-COM DLL has no effect on the registry, and probably causes regsvr32 to return an error.

    Hope this helps.

    Peter Cooper

  8. #8
    Gold Lounger
    Join Date
    Dec 2000
    Location
    Hollywood (sorta), California, USA
    Posts
    2,759
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: What are the pros and cons of registering ANY DLL

    Now that's a cogent reply. Whats say Chris? Now, say no more!

    (Thanks, Peter)
    Kevin <IMG SRC=http://www.wopr.com/w3tuserpics/Kevin_sig.gif alt="Keep the change, ya filthy animal...">
    <img src=/w3timages/blackline.gif width=33% height=2><img src=/w3timages/redline.gif width=33% height=2><img src=/w3timages/blackline.gif width=33% height=2>

  9. #9
    Gold Lounger
    Join Date
    Dec 2000
    Location
    New Hampshire, USA
    Posts
    3,386
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: What are the pros and cons of registering ANY DLL

    I don't have the time to provide all hte details now, but not ALL DLLs are equal.

    Unless the DLL is COM based, adding references to it or trying to register it is pointless. It just exports functions.

    For example, I made the mistake of registering a DLL this week that was not COM based. I had a heck of a time getting rid of references.

    I ended up just putting the critter in F:WinNTsystem32 and refering to the DLL in a Declare statement.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •