Hi
Using COM+ is one option. A better way would be to use
the .Net Remoting feature as it is the recommended way....
It gives you a better maintainability and also the fact
that using the HTTP channels of remoting u can call
components across firewalls as by default it uses SOAP
protocol. For more info on Remoting check out MSDN. It
has a lot of examples.
In case you need a sample, do mail me at
rs_tiin@hotmail .com and would be happy to send u the same
hth
regards,
sr
[color=blue]
>-----Original Message-----
>Hi all !
>I've following question :
>There is ASP .NET main program that runs on local machine
>and wants to call some routine in some DLL that[/color]
phisically[color=blue]
>is on remote machine.
>I know that I should create and registrate this DLL as
>server COM+ application on remote machine and as client
>COM+ application on local machine - proxy.
>Does anybody know how should I create "server".ms i and
>"client".ms i files ?
>Thanks in advance , Miri.
>.
>[/color]
Using COM+ is one option. A better way would be to use
the .Net Remoting feature as it is the recommended way....
It gives you a better maintainability and also the fact
that using the HTTP channels of remoting u can call
components across firewalls as by default it uses SOAP
protocol. For more info on Remoting check out MSDN. It
has a lot of examples.
In case you need a sample, do mail me at
rs_tiin@hotmail .com and would be happy to send u the same
hth
regards,
sr
[color=blue]
>-----Original Message-----
>Hi all !
>I've following question :
>There is ASP .NET main program that runs on local machine
>and wants to call some routine in some DLL that[/color]
phisically[color=blue]
>is on remote machine.
>I know that I should create and registrate this DLL as
>server COM+ application on remote machine and as client
>COM+ application on local machine - proxy.
>Does anybody know how should I create "server".ms i and
>"client".ms i files ?
>Thanks in advance , Miri.
>.
>[/color]