Registering for Policy Refresh Notification in c#

[Fred]

Hello,

I've a question about implementing a group policy notification in c#. I've
read the MSDN about this and they have a sample in C++.
http://msdn.microsoft.com/library/de...tification.asp
(Sorry for the wrap!)
I can create the events for the machine and user with the CreateEvent API
en register them with the RegisterGPNotif ication API. But when want to do
that in a thread created in c# and call there the WaitForSingleOb ject API
then i've got a problem that the thread won't stop without a call to
gpupdate. According to the MSDN doc is that correct:
<qoute>
If a thread makes an unmanaged call into the operating system that has
blocked the thread in unmanaged code, the runtime will not take control of
it for Thread.Interrup t or Thread.Abort. In the case of Thread.Abort, the
runtime marks the thread for Abort and takes control of it when it re-enters
managed code.
</qoute>
So my question is, is there a work around or a better solution for
implementing a Policy Refresh Notification?

TIA

Fred

[Chris Jobson]

"Fred" <fred(geenspam) @testomgeving.c om> wrote in message
news:Ou******** ******@TK2MSFTN GP12.phx.gbl...

Hello,

I've a question about implementing a group policy notification in c#. I've
read the MSDN about this and they have a sample in C++.
http://msdn.microsoft.com/library/de...tification.asp
(Sorry for the wrap!)
I can create the events for the machine and user with the CreateEvent API
en register them with the RegisterGPNotif ication API. But when want to do
that in a thread created in c# and call there the WaitForSingleOb ject API
then i've got a problem that the thread won't stop without a call to
gpupdate. According to the MSDN doc is that correct:
<qoute>
If a thread makes an unmanaged call into the operating system that has
blocked the thread in unmanaged code, the runtime will not take control of
it for Thread.Interrup t or Thread.Abort. In the case of Thread.Abort, the
runtime marks the thread for Abort and takes control of it when it
re-enters managed code.
</qoute>
So my question is, is there a work around or a better solution for
implementing a Policy Refresh Notification?

How about creating a second event and use WaitForMultiple Objects to make the
thread wait on either event being signalled? When you want to interrupt or
abort the thread just signal the second event. The thread will know which
event was signalled by the return value from WaitForMultiple Objects.

Chris Jobson