Dear All,
I have made a serviced component which is used for my webpages logins.
I have tested the component and connecting to it via ASPX (VB) when the component is registered on the same pc / server as the application that uses the componet resources/class.
In the user application I made a reference to the serviced component at design time as per many books say and all works fine, Problem now is that I want to have the serviced component on another server...So how to get my application on server *A to be able to use serviced component othat is registered on server *B.

I want to use this component as a standard for all logins both by exe applications and by web pages. The exes need to log into sql database and log some events that happen as well as when users wnat to see what has happened with the exe processes can see the logged events...
Any help appreciated.

Is dcom the only way to do this if so how to set things up?

cheers An English man in Sweden*

Hi there,

You failed to mention if the serviced component was developed in .NET or any other tech. If it is a .NET component the solution can easily be solved with something called .NET Remoting. I guess that technology can be used anyway but its easier with a serviced .NET component.

As i said, one way to do this is to use .NET Remoting. Remoting is the .NET successor of DCOM and is based on an open architecture that supports multiple protocols etc. .NET Remoting has built-in support for things like security etc, and is much easier to get started with, compared with DCOM.

The other option i could suggest is to use.NET WebServices, which i guess (im not really sure) is more standardcompliant and lightweight in comparison to a .NET Remoting. Thereby more compatible than .NET Remoting.

I think i personally would use .NET Remoting for this task, it is very flexible and is binded to a port through something called a Channel.

You can find pretty good samples and articles on .NET Remoting on www.c-sharpcorner.com.

Im currently reading a pretty good book about .NET Remoting but i havent got the ISBN here. If your interested, give me a shout and ill fix the ISBN tomorrow.

/Martin

remoting does not have built in support for security,

althoug there's a Remoting sink example from Microsoft for security, Security is it's weak point. Also there's no really good remoting environment, you need to develop your own or rely on IIS and HTTP (overhead).

HI, yes the component is made in VB.net
inetrested in any way you can help in this matter.
cheers for know.