B
boohaus
I was advised to post here instead of Project Server group, so here goes...
I have created a custom event handler, following the MSDN article
(http://msdn2.microsoft.com/en-us/library/bb968451.aspx). ; I followed the
article to the letter until I needed to tweak it for my own application. As
I was debugging it I realized the event handler (Notifications OnSending) is
invoked twice. In PWA I have only one instance of the event handler
registered. There's only one version of the .dll registered in the GAC. Just
for measure, I uninstall event handlers out of PWA and the GAC then reboot
the server and my workstation and re-install everything, in order.
Moreover, I place Debug.WriteLine statements inside of my functions and
notice the second instance of the handler is not getting called at the same
point in the first instance. I came to do this because as I would run remote
debugging, the debug pointer (whatever it's called) was jumping back and
forth in the same function(s). I guess this is because the debugger can
trace through only one source window even though the machine is stepping
through multiple instances of the same object?
Any ideas why the event handler is called twice? Also, I want to point out
that everything else, more or less, works as it should. How this issue
affects me is that two separate threads process the same
notificationDataXmlDocument so my notification gets skewed.
I have created a custom event handler, following the MSDN article
(http://msdn2.microsoft.com/en-us/library/bb968451.aspx). ; I followed the
article to the letter until I needed to tweak it for my own application. As
I was debugging it I realized the event handler (Notifications OnSending) is
invoked twice. In PWA I have only one instance of the event handler
registered. There's only one version of the .dll registered in the GAC. Just
for measure, I uninstall event handlers out of PWA and the GAC then reboot
the server and my workstation and re-install everything, in order.
Moreover, I place Debug.WriteLine statements inside of my functions and
notice the second instance of the handler is not getting called at the same
point in the first instance. I came to do this because as I would run remote
debugging, the debug pointer (whatever it's called) was jumping back and
forth in the same function(s). I guess this is because the debugger can
trace through only one source window even though the machine is stepping
through multiple instances of the same object?
Any ideas why the event handler is called twice? Also, I want to point out
that everything else, more or less, works as it should. How this issue
affects me is that two separate threads process the same
notificationDataXmlDocument so my notification gets skewed.