A C++ project for creating WinRT based designs.

• This uses a C++ VS Test project to provide code examples.
• It enables creation and implementation of WinRT Interface Definition Language (aka Microsoft Interface Definition Language MIDL) types.
• Show code examples, an important aspect of validating API designs.
• Enables executing the implementation and the example use.

#include "pch.h"

TEST_CLASS(DemonstrateSystemLauncher)
{
    TEST_METHOD(LaunchExample)
    {
        // ... sample code
    }
};

The WinRT Tools for C++ extension improves the .idl file editing experience and is highly recommended.

Independent from the primary goal, this sample demonstrate the Work In Isolation technique. This is applicable to any language or environment, this case shows C++/WinRT/Visual Studio IDE/github as the example.

Not all projects can use github. But given its scope, it is a great way to share links to examples and invites participation.

Making setup easy is important or ensuring the ability to access it remotely from the context where it is needed.

• Visual Studio offers templates for creating projects, this this is often a best first step.

• After creating the project consider cleaning it up as the default templates can be simplified. Fewer files, folders and a structure that makes working int the code simple.

• Add the dependent libraries as NuGet packages or use vcpkg. For Windows code Windows Implementation Libraries (wil) is essential. Use other libraries make production and consumption of designs simpler.

• Pick descriptive names and a README.md to introduce the project.

• Push to remote!

In the environment where you need to be able to help others on coding issues, keep the project nearby. Keeping it loaded in the IDE makes access fastest.

Questions can be answered with "this compiles" in seconds to to a few minutes. "this runs" is also possible with a little more time investment.

Make the project easy to launch, pin it to the Visual Studio TaskBar JumpList.

Be aware of the costs of multi-tasking.

Try to directly demonstrate a solution to a problem someone is having or to demonstrate an alternative solution.

Copy and paste the snippet into the communication medium if that is sufficient. But commonly pushing to the remote and sharing a link to github is needed.

Use this as an opportunity to give the method a good descriptive name.

See if the solution generalizes and if so, describe it in those terms.

To set expectations, qualify your confidence in the solutions ability to solve the problem. Be humble and the possibility that you don't fully understand the question.

When you advocate for a specific design approach creating the solution in the form of code that can be executed to communicate it is very effective. It can also reduce the cost of work if the team realizes that the problem can be resolved simply with a working POC to start from.

If the problem is API design shape, the abstractions are the output of the design .idl files that compile.

• Leverage your unique combination of knowledge and target the most commonly encountered issues of your team or the community that you operate in.
• Build up a library of solutions.
• Learn about the coding environment you are helping on deepest degree.
• Become fluent through practice.
• Contribute to the success of others.

Use package managers to access useful libraries and tools needed by the code being created.

For the Windows operating system developers, see this description for details on how to apply work in isolation to work that depends on internal Windows APIs.

For Marina and others who asked me to share what I know.