


A sneaky way to make sure nobody assigns test failures to your team

Are Windows Runtime asynchronous operations guaranteed to complete?

If you say that your minimum requirements are the Universal contract, then you need to probe for anything beyond that

How can I check whether a Windows Runtime object supports a member before I try to use it?

Why not just share a single event across all critical section?

The security check happens at the acquisition of the handle

Further refinements to the attempt to create a type-dependent expression that is always false
