Because Visual Studio stores the startup project in the user settings for a solution, when one is not set up yet -- such as after cloning the repo locally and running it for the first time -- it will default to the first project listed in the .sln file.
Since the CLI project is the end goal, switching up the order in the file to fit this behavior.

SlavaVedernikov#100

It makes sense that the default execution should be against something that already exists in the repository.
Tried to make this match the 'draw-diagrams.bat' file in the directory, the output doesn't quite match any more.

SlavaVedernikov#100

SlavaVedernikov#100

This helps bring in a consistent set of settings that apply to the codebase as a whole, and do not depend on the individual's IDE settings.
This also helps be explicit on what analyzer settings are enforced vs. what ones the project does not wish to adhere to.

SlavaVedernikov#100

This way it's easy to test a change against all examples

This way it's easy enough to execute all executions in a single go.

Removing the top level interfaces per PR feedback.
SlavaVedernikov#104 (comment)