Source control and build–part 3
(This is the result of 1 hour per day auto-challenge as a full cycle developer)
I need to put somewhere the sources – GitHub seems the obvious choice. So I created https://github.com/ignatandrei/infoValutar/ and put there the project.
Now trying to help others to see the final result – and here GitHub actions can help build the project. GitHub actions already has a .NET Core workflow . Moved to 3.0.100 version of .NET Core and also replacing dotnet build with dotnet publish to have a single file trimmed (https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-3-0 ). Making error once ( the first argument of build should be the project , not the switches) and , after this, receiving error from github
MSBUILD : error MSB1009: Project file does not exist.
Remember the / vs \ in Linux and Windows ?
dotnet publish InfoValutar\InfoValutarDOS\InfoValutarDOS.csproj -r win10-x64 -p:PublishSingleFile=true –self-contained
works in Windows, but not in Linux , but
dotnet publish InfoValutar/InfoValutarDOS/InfoValutarDOS.csproj -r win10-x64 -p:PublishSingleFile=true –self-contained
works both in Windows and Linux
Now reading about how to create a release.
The most comprehensive is https://github.com/actions/upload-release-asset . However, I need also a change log and a way to say automatically what release is.So I need the current day and time to name the release. However, too much for this kind – and not mention that GitHub Actions are in beta. So no need to spend too much on this. – better to go to AzureDevOps and let Azure DevOps handle the process.
But , for the moment, I have the Source Control activated and an automatic build of the first projectAnd one hour passes...
(This is the result of 1 hour per day auto-challenge as a full cycle developer for an exchange rates application)