Add real-world code

[ric15ni]

Reference version

2.0.1-preview

Background and motivation

If we want procedures like testing and coverage, once implemented and tested here, to be suitable for at least the majority of real-world projects, we need some "real" code to test.

For starters, there is no meaningful way to "arrange, act, assert" when testing parameterless methods that always returns the same constant. But it's more complex than this. We should be able to meaningfully test Coverlet exclusions, determine whether we need some sort of per-project testing customization vs. a one-size-fits-all default.runsettings file, and the list grows longer with each hour I spend on this.

Proposed enhancement

AaaLib should contain some real-world, or at least real-world-like, code.

It should also contain different kinds of projects:

• a multi-target, multi-platform library - currently the only kind of project AaaLib contains;
• a console executable that uses all possible Microsoft extensions (hosting, logging, command line, file systems, etc.);
• an analyzer and a source generator (maybe in the same project);
• given the latest direction we are taking with regard to user interfaces, an Avalonia application (complete with setup for all necessary platforms) seems to be good to have too;
• ...did I forget anything? I'm almost sure the picture is not complete yet.

Once we have projects of different kinds to work on, we will also be able to add e.g. integration tests as briefly suggested in #10.

Implementation proposals

Code can be brought in from tutorials found on the web, at least initially.

Also, with all due respect to the late Douglas Adams, the Aaa class has to go. It was good as a first, minimal example to start building Cake scripts and GitHub workflows, but once we have "real" code, it has no place here any longer.

Usage examples

n/a

Risks

Of course the removal of the Aaa class is a breaking change. I don't expect much customer impact, though, as AaaLib was never meant to be actually used as a dependency.

Additional information

No response

[rdeago]

I have converted this to a discussion because we'd better split it up into smaller issues.

Glad you didn't mention web projects - we're not ready to go down that rabbit hole yet.

I'm going to open and assign some issues, then list them here.

[rdeago]

Also, with all due respect to the late Douglas Adams, the Aaa class has to go. It was good as a first, minimal example to start building Cake scripts and GitHub workflows, but once we have "real" code, it has no place here any longer.

Agreed. Just closed #2 as "won't fix" accordingly.