Repairing the build and versioning–part 15

Now , after copy the plugins, the build is not working.

Thnking about the build events, I realize that to find same copy command on Linux and Windows is difficult – so Windows it is.

( and, BTW , In LInux the macro $(SolutionDir ) does not work use  repoRoot


Switch windows-latest on 

Now tests are failing – repairing the tests.

I realize that I cannot build just the csproj – the solution sln knows the order in which to build the projects- but the .csproj does not. So now building the sln and then publish

Now giving error in Github, but not on local. More, there was a not repeatable . I figured was because of the parallel builds so this is the final line

dotnet build –configuration Release InfoValutar/InfoValutar.sln /m:1

Now it works!

The only programming thing that I have done is to add versioning , . I do tend to say that the URL is a Unique Identifier – so I want the versioning be part of the URL.

As advised by

I added the pacakage Microsoft.AspNetCore.Mvc.Versioning and


and on the controller

[ApiVersion( “1.0” )]


and now I can access


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