The static Raise method is synchronous, as are the invocation of the Event
Sinks. For the event sinks we implemented in EIF, this made the most sense
given that the trace sink is very efficient at getting the event into the
trace buffer and returning, while neither the WMI nor event log sink had
perf requirements which merited using an async approach.
You can implement a custom event sink which handles the event
asynchronously, but we don't yet have samples or best-pactices for doing
this.
David [MSFT]
--------------------
| From: "Steve Miller" <stevemi@avanade.com>
| Subject: Raise method mechanics.
[quoted text clipped - 8 lines]
| NNTP-Posting-Host: pcp518123pcs.nash01.tn.comcast.net 68.53.141.212
| Path:
cpmsftngxa07.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP08
phx.gbl!tk2msftngp13.phx.gbl
| Xref: cpmsftngxa07.phx.gbl microsoft.public.vsnet.enterprise.tools:1445
| X-Tomcat-NG: microsoft.public.vsnet.enterprise.tools
|
| How is the Raise method implemented: synchronously or asynchronously?
|
| Steve Miller