User shutdown of Vusta terminates dependant processes before ancestors?
I read an article describing shutdown changes in Vista:
http://windowssdk.msdn.microsoft.com/en-us/library/ms700677.aspx
In some testing I was doing with the July CTP, I noticed that if an application (A) starts another application (B) that has no gui, and then the user shuts down, if A registers an objection (using the new api), B is still killed before A has a chance to close. Process explorer does show that B was started by A, but there doesn't seem to be any regard for this when shutdown occurs. To be more clear:
1) Application A is started
2) A starts application B
3) The user makes changes to A
4) The user issues a shutdown. A registers an objection, and pops up a message asking the user if they want to save their changes.
5) Application B is killed by Vista before the user has a chance to respond to the dialog raised in step 4.
I was wondering if this behaviour is on purpose, as it is not clearly specified in the msdn article above and will have a siginificant impact on my (and I am guessing many other) applications. If it is not on purpose, will it be changed by the time Vista is released?
If there is any additional documentation, please point me in the right direction.
Thanks,
Jason Hinsperger
Sybase iAnywhere
