Results 1 to 3 of 3

Thread: LAN Server Dll Usage on Client Machine

  1. #1

    Thread Starter
    New Member
    Join Date
    Nov 2000
    Location
    Toronto, Canada
    Posts
    7

    Unhappy

    Hi Everyone,

    The Scenario:

    A LAN of 2 pc's both running WIN 2K. PC "A" & "B"

    The Problem:

    On PC "A" I develped a DLL which performs a simple math calculation, while compling this DLL I checked the REMOTE SERVER option so that I could use this dll remotely and also MTS-Enabled it. Then I developed a VB application which uses this DLL. Everything is working fine on my PC. Mind you that I use the CreateObject("Prog.Class","My Server") to provide refrence to the DLL.

    Now we take the application to the other PC , PC "B", on the lan and use it. Error is offcourse , DLL not in Local Registery...Then I registred it manually using regsvr32.exe. After this the application was working fine.

    One way to handel this is to use the shell command to run regsvr32 to register the DLL.

    But I dont like it, what If this was a real LAN in an office and the DLL was moved from one server to the other ? Is their a better approach ?

    I am looking for a proffesional way here ?

    Wating....

    shaherayr
    [email protected]
    http://www.thequreshi.com
    Shaheryar Jamshaid Rahim Qureshi
    [email protected]
    www.thequreshi.com

  2. #2
    Hyperactive Member tumblingdown's Avatar
    Join Date
    Mar 2000
    Posts
    362
    But I dont like it, what If this was a real LAN in an office and the DLL was moved from one server to the other ? Is their a better approach ?
    ...then presumabley you would have some kind of production release procedure, and this would take care of registration issues.


    td.


    "One logical slip and an entire scientific edifice comes tumbling down." - Robert M. Pirsig


    [email protected]

    "but if Einstein is right and God is in the details, reality requires that we sometimes get religion." - Scott Meyers.

  3. #3
    Guru Clunietp's Avatar
    Join Date
    Oct 1999
    Location
    USA
    Posts
    1,844
    Register the DLL with COM+ on computer A. Export the 'application', which should generate the MSI (install) file which you then run on computer B. You may then use CreateObject (don't specify a server name) on computer B to activate the component on computer A


    Tom

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