


How do I use C++/WinRT to implement a classic COM interface that derives from another classic COM interface?
guid_of.
Why does the value of my XAML Slider change when I updated its range?

Virtual desktops are a window management feature, not a performance feature

It rather involved being on the other side of this airtight hatchway: Planting files onto a custom PATH

What will be placed in the output parameter if the function fails?

Why can’t you return an IAsyncAction from a coroutine that also does a co_await?

When I ask the GetIpAddrTable function to sort the results, how are they sorted?
Old New Thing

When you set Windows 10 to allow only Windows Store apps, it allows them to be installed by anyone, not just the Store app
It's about the source of the program, not the delivery mechanism.

How do I use C++/WinRT to implement a classic COM interface that derives from another classic COM interface?
You can specialize guid_of.

Why does the value of my XAML Slider change when I updated its range?
Releasing the spring.

Virtual desktops are a window management feature, not a performance feature
Everything runs the same as it did before.

It rather involved being on the other side of this airtight hatchway: Planting files onto a custom PATH
Adding a directory to the PATH comes with obligations.

What will be placed in the output parameter if the function fails?
Officially, it could be anything. In practice, though, there are some constraints.

Why can’t you return an IAsyncAction from a coroutine that also does a co_await?
You already returned. No take-backs.

When I ask the GetIpAddrTable function to sort the results, how are they sorted?
Nothing particularly fancy. Just plain numerical order.

