Results 1 to 2 of 2

Thread: DLL registration. Somebody tell me the truth, dammit!

  1. #1

    Thread Starter
    Member
    Join Date
    Aug 2000
    Posts
    45
    "You want the truth? YOU CANNOT HANDLE THE TRUTH!"

    *cough*

    Okay, I just got this question on my transcender-cross-your-fingers-and-hope-to-pass practice test:

    "What two methods can be used to register an out of process component with the operating system on a developer's computer?"

    ANSWER: You can use the RegSvr32 program or compile it in VB. Either method will register it with the operating system on the developer's computer.

    I thought that creating a package and deployment package and using the generated setup.exe would register it to the developers computer as well. Is there some reason why this isn't an option?
    -Gregg
    -NoOBie At LaRg3

  2. #2
    Fanatic Member
    Join Date
    Mar 2000
    Location
    That posh bit of England known as Buckinghamshire
    Posts
    658
    The setup program uses regsvr32 to register the dll, that is why. You dont need to install a package on the developers computer becuase the developer will have all of the required files.
    Iain, thats with an i by the way!

Posting Permissions

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



Click Here to Expand Forum to Full Width