Web Services Auxiliary VI in 2011

Question

In LV 2010, a Web Service Auxiliary VI began to run upon web service deployment. After upgrading to 2011 [f2], auxiliary VI's no longer run upon deployment of their web service. I have validated this with a test project:
1. Create a new auxiliary VI that fills a boolean global with the value TRUE.
2. Add a new web service build. Include the VI as an "Auxiliary VI" in the Service VI's portion of the build specs.
3. Build and deploy the web service. Check the global front panel and observe that the boolean is still FALSE.
Since this behavior pretty much nukes the entire concept of Aux VI's, I'm curious what's going on [well, I also want it to not happen in a desperate way]. Can anybody else verify this?

Answer 1

Well, that was clearly not what was causing the problem, but the fact remains that I had a working webservice before upgrading [it's hard to tell right now whether the upgrade to 2011 or f2 caused the problem] and now I've got the following problem:
First a description of what I'm doing. I have an Auxiliary VI which enables and requests value change notifications for two NSV's. The notification refnum [cast as an int] and SV names are sent to globals. As an Aux VI, this code is automatically run upon deployment of the webservice. [image below]
Next, I have a service VI [image below]. The notification refum is cast back to the correct notification type, and SV value change notifications are registered for. The registration is passed to an event structure set to run when either of the SV values change. This web service is called by the web client periodically [the long expiration time (~1 day) and lack of a loop for the event structure are required for my intended web service behavior].
In LV 2010 SP1, this did exactly what I wanted it to do: the client accesses the service VI, but waits for a response until the data generator changes the SV values. I considered this a fairly clever and lightweight solution for my very-low-trigger-rate application.
Now, with LV 2011 [f2], the event structure never triggers. I've verified that the notification refnum and SV names provided to the service VI are correct. I also checked that this process works [the event structure executes] when the above two diagrams are placed in a two-pane sequence structure. The Aux VI and Service VI's should belong to the same application instance, and I can't imagine this having changed [else what is the point of an Aux VI?]. But the evidence still seems to indicate that the notification refnum passed from the Aux VI is no longer valid when used by the Service VI.
Any thoughts?