One possible solution would be:
A windows service that uses (hosts) a COM+ component and other applications
use loosely coupled events ( LCE) to recieve notifications as required.
The COM+ component could be either a library or server component.
--
HTH
Ollie Riches
http://www.phoneanalyser.net
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a programmer
helping programmers.
<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi,
>
> I am tasked with writing a COM+ application in C# in which the program,
> when started, will sit and poll for something (not important here), and
> when that condition occurs, then I publish events so that subscribing
> applications can do something. I've written a basic shell of a program
> that I can install as a COM+ application (w/ gacutil, regsvcs, etc),
> but my question is, since a COM+ application has no user interface, or
> wait state like a Windows program with a timer, how do I make a COM+
> application just sit there and do something at a partuicular interval?
> I see there is the System.Threading.Timer class that I could possibly
> use, but where would I instantiate it in the class? Are there any
> startup methods that I can override?
>
> All the COM+ examples I've seen have the COM+ methods invoked by a
> client process only.
>
> Any ideas?
>
> TIA,
> Robbie
>