raising events from a windows service -- dotnet framework

dotnet framework : raising events from a windows service

Chris, Master of All Things Insignificant
12/30/2004 2:40:31 PM

I believe that with .Net you are going to have to use remoting to do this.
My question for you is:

If both these programs are running on the same system, why not have the
client program check for the new records and handle them internallly?

Chris

[quoted text, click to view]

Trevor Braun
12/30/2004 3:17:36 PM

I have a windows service that generates events when it finds certain
database information. That is, the service runs, and on a timer event, it
checks a few database tables for new records. If the new records have been
created, it generates the NewRecord event.

I would like to have a client application subscribe to the events generated
by the windows service, but when I attempt to use the service as a reference
in my VS.NET project, I get an error that says I can only reference DLL's.

Can anyone recommend a way for me to "accomplish my mission"?

Thanks,
Trevor Braun

Trevor Braun
12/30/2004 4:21:19 PM

Thanks for the thoughts.
I didn't mean to give the impression that the client application would be
running on the same machine, however at present (during development) that
would be the case.
I understand that remoting will be required for the eventual deployment, but
for building and testing the windows service, I just wanted a simple client
application that could monitor the events being raised by the service. How
will remoting affect this? BTW, I haven't used .NET remoting before.

Trevor

[quoted text, click to view]

Trevor Braun
12/30/2004 5:24:06 PM

Thanks for the terrific explanation. I'll do some more research on the
remoting before I continue.

Trevor

[quoted text, click to view]

Trevor Braun
12/30/2004 8:12:45 PM

I've looked at the remoting stuff, and gotten a sample (remote DLL) working,
but still not across applications.

I'm lost as to how I can have the client application reference events in the
server application. Do you know of any examples where I can see a server
application raising an event in a client application?

Thanks,
Trevor Braun

[quoted text, click to view]

Trevor Braun
12/30/2004 8:23:24 PM

Richard Grimes [MVP]
12/30/2004 10:14:54 PM

[quoted text, click to view]

Stop there. Client *application*. Windows *service*. You have two processes.

[quoted text, click to view]

That's because the memory address for your event handler is only valid in
the current process. Your service is another process.

[quoted text, click to view]

You have to use .NET remoting. .NET remoting is used to marshal calls
between two AppDomains. Those AppDomains could be in the same process, could
be in two different processes on the same machine (your situation) or in two
different processes on two different machines.

Note that if the service is running as LOCALSYSTEM it won't be able to raise
an even to a client on another machine because LOCALSYSTEM does not network
privileges.

It depends on what sort of data you pass in the event, if its simple data
then I would favour use a lightweight solution like a socket to pass the
data to the client. (If you have some database rowobject, you just need to
serialize the object, send it through the socket and deserialize it on the
client side.)

Richard
--
www.richardgrimes.com
my email evpuneqt@zicf.bet is encrypted with ROT13 (www.rot13.org)

Dan Kelley
12/31/2004 1:43:01 AM

This is where things can get complicated, depending on your application
needs. If you are using remoting, it may be better to forget about using
events in the conventional sense. Instead, I would suggest designing the
system so clients call a "subscribe" method on the service. The service will
then maintain a list of subscribed clients, and when needed, sends a
"message" to the client. Problems may occur if for some reason, sending this
message fails (e.g. network problem, or client machine crashes, etc.) Then
server would need to handle exception and remove client from list. But what
if the client is still reachable, and the problem was temporary. Now they are
not receiveing the events? Probably a few solutions, one would be to have the
client send a mesasge to the server if it had not received a message for X
intervals.

Enough rambling though. If you are looking for specific remoting answers, I
would recommend you post a mesage on the
microsoft.public.dotnet.framework.remoting group, as Ken Kolda and Sam
Santiago generally give very good advice there on a lot of remoting queries.

HTH
Dan

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet framework

View Other Months
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008

home · blog · groups

Questions? Comments? Contact the dn