HELP on "C" DLL internal code for LAN's and WAN's use

[Tom Thorpe]

To all wizards:

I have a "C" DLL file already built and running, but I want to have the DLL
accessible(callable) from anyway within a LAN and/or WAN( and even
multi-WAN's), or even on a PC. I built the DLL file, via VC++'s (v6.0) ATL
COM AppWizard area, and it works quite well. But as for using the DLL file
on LAN's and Wan's, do I need to add any more code into the DLL file, so it
will work on/under a network and be callable anywhere on a LAN's or WAN's or
even on standalones by any and all application(s). If I need some
additional code, can you tell me why, and can I get it in simple "C" source
code. Any help would surely be greatly appreciated. Thanks(TIA),

Tom.

 

[ramakrishnat]

An ordinary DLL can't be accessed across different machines.But since
you built the DLL using ATL COM wizard it is a COM dll.COM provides
something known as location transperancy meaning no matter where the
DLL is it can be accessed,even across different machine boundaries.All
u need to do is,take the dll to Component services in Admin tools and
create an app install the dll under the app.Next,generate an app proxy
which u can do from the Component services,take the proxy to a client
machine and install.And make sure that the client which uses the COM
dll has enough privileges to do so....

 

[Keith Thompson]

To all wizards:

I have a "C" DLL file already built and running, but I want to have the DLL
accessible(callable) from anyway within a LAN and/or WAN( and even
multi-WAN's), or even on a PC.

[snip]

This is off-topic in comp.lang.c. Followups redirected.

 

[Mark McIntyre]

An ordinary DLL can't be accessed across different machines.

This isn't true, but since its horribly offtopic in CLC, all we can do
is redirect the user to look for a group specialising in distributed
processing.