Documentation and refactoring for plugins and wrong code coverage – part 12

I realized that will be no documentation for plugins – until I create one .

Figured also that each plugin should have a name  -to understand from where he grabs data – so some code involved code.


Asking when and if the plugins are copied to the application  – not found yet an answer…


Now the user can choose what bank he wants to see data ? We could do this for the console application –  and I think that is the moment to play with Icaza  Gui Terminal  – Created buttons to display plugins (NBR and ECB ). Will not work if many plugins will come – but it is ok for the moment.

Discovered the window for code coverage – read

Some error when writing the .runsettings file – discovered from command line ( GUI does not show)

Reading the docs , , it says that is not available for community…

Back to square 1 after 1 hour- just made documentation.

And one hour passes...
(This is the result of 1 hour per day auto-challenge as a full cycle developer for an exchange rates application)
( You can see the sources at )
2Reading NBR from internet
3Source control and build
4Badge and test
5CI and action
6Artifacts and dotnet try
7Docker with .NET Try
9Intermezzo - Various implementations for programmers
10Intermezzo - similar code - options
11Plugin implementation
12GUI for console
14Plugin in .NET Core 3
15Build and Versioning
16Add swagger
17Docker - first part
18Docker - second part
19Docker - build Azure
20Pipeline send to Docker Hub
21Play with Docker - online
22Run VSCode and Docker
23Deploy Azure
24VSCode see tests and powershell
25Code Coverage
26Database in Azure
27Sql In Memory or Azure
28Azure ConString, RSS
29Middleware for backward compatibility