Just pass data back and forth. Remoting is probably your best bet for this
type of access. Basically you have a class on your service that is
remotable. You will have a method in that class like "MyStatClass
GetStats()" that returns a stats object you built that contains all the
counters and stuff you need as fields of that class. That class gets
marshalled back to your client program as an object just like if you newed
it up locally. Use it like any other class and get your data from the
properies and/or fields. Remember to make your counters thread safe on
your service. hth
--
William Stacey, MVP
[quoted text, click to view] "Eirc" <anonymous@discussions.microsoft.com> wrote in message
news:94AF3817-4F7A-42CC-885F-4449713C5211@microsoft.com...
> I have a service that is written in .net and is running on our server. I
want to develop a remote console that would be a .net *.exe that would run
on a remote machine and connect to the specified service. I want this
remote console to be able to connect to the service and report back stats
from the service. The service could expose properties or methods with
real-time counters and status information for that service. I need to
connect and see that real-time data.
[quoted text, click to view] >
> Most of you will reply with one word; Remoting, however as i understand
Remoting it is much like DCOM. In this case i don't need to use the logic
of the service locally, i need to connect to an in-process service and
extract real-time data. If remoting is the answer, please provide some
insight as to how remoting can connect to a in-process object and report
back real-time information about the object.
[quoted text, click to view] >
> thanks eric.
>