The dangerous implementations of the IMemoryBufferReference.Closed
event
The useless IMemoryBufferReference.Closed
event
Accessing a block of memory represented by a Windows Runtime IMemoryBuffer
The case of the fail-fast trying to log a caught exception
Implementing two-phase initialization with ATL
Getting a strong reference from the this
pointer too soon
What is a hard error, and what makes it harder than an easy error?
C++/WinRT gotcha: Not all exceptions derive from hresult_error
std::bad_alloc
.
In C++/WinRT, how can I await multiple coroutines and capture the results?, part 3
void
, and questioning our life choices.