My personal knowledge base, online.
Content about software development concepts, architectures, and practical tips.
Go the the directory of the .NET core project and run dotnet publish:
dotnet publish --os linux --arch x64 /t:PublishContainer -p ContainerArchiveOutputPath=./images/xxx.tar.gzAdditional information on Stackoverflow: https://stackoverflow.com/questions/58916308/kubernetes-deploy-with-tar-docker-image
Create a folder, for example /app/dotnet6, and assign ownership to the right user:
sudo mkdir /app/dotnet6
sudo chown -R pi /app/Download the .NET 6 SDK at Microsoft:
wget https://download.visualstudio.microsoft.com/download/pr/adcd9310-5072-4179-9b8b-16563b897995/15a7595966f488c74909e4a9273c0e24/dotnet-sdk-6.0.100-linux-arm64.tar.gzExtract the tar.gz file in the /app/dotnet6 directory:
sudo tar zxf dotnet-sdk-6.0.100-linux-arm64.tar.gz -C /app/dotnet6Test the .NET6 installation by browsing to the installation directory and execute the dotnet –info command:
cd /app/dotnet6
./dotnet --info
.NET SDK (reflecting any global.json):
Version: 5.0.101
Commit: d05174dc5a
Runtime Environment:
OS Name: debian
OS Version: 10
OS Platform: Linux
RID: debian.10-arm64
Base Path: /app/dotnet/sdk/5.0.101/
Host (useful for support):
Version: 5.0.1
Commit: b02e13abab
.NET SDKs installed:
5.0.101 [/app/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 5.0.1 [/app/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 5.0.1 [/app/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET runtimes or SDKs:
https://aka.ms/dotnet-downloadGetting the source code of my home automation project on Github was a first step. Now, I’m ready to post some components on NuGet as well. This makes it easier to manage the packages and reduces the dependencies between my Visual Studio projects.
I ran into a challenge though: how could I easily upload my projects to NuGet without having to use the command line? Luckily, Visual Studio has something called Post-build event command line.
The command put into this block is executed after finishing the build. The only thing you need to do manually is change the package version, otherwise NuGet will rightfully decline the push (the version already exists).
Depending on your directory and project structure you should be able to get the command below up and running. You can easily test this in the Command Prompt, just make sure you browse to the right target directory.
cd bin\Debug && dotnet nuget push *.nupkg -k xxx -s https://api.nuget.org/v3/index.json --skip-duplicateOf course, you should replace the xxx with the NuGet API key.
I started working on my home automation project in 2020. I started with a simple backup script that copies the source code to a second hard drive, just in case the primary hard drive fails. When my code base started to grow I extended the script to create a (daily) second copy on OneDrive. From a backup perspective this is working fine, but it does not give me versioning and source control. Luckily, Github exists. Microsoft developed a Github extension for Visual Studio.
Make sure you update your Visual Studio installation before you install the extension. You also need to install Git for Windows. Additionally you need a Github account. After that, publishing an existing project to Github is pretty straightforward.
Open the command line and browse to the directory of the project. Execute a git init.
D:\>cd DataMario\Ontwikkeling\IoT\Verhaeg.IoT.Geofencing.Sensor
D:\DataMario\Ontwikkeling\IoT\Verhaeg.IoT.Geofencing.Sensor>git init
Initialized empty Git repository in D:/DataMario/Ontwikkeling/IoT/Verhaeg.IoT.Geofencing.Sensor/.git/
D:\DataMario\Ontwikkeling\IoT\Verhaeg.IoT.Geofencing.Sensor>Open Visual Studio and copy/paste an existing gitignore file to exclude configuration files that could include passwords.
Then push the project to Git:
And finally, define the Git repository details.
Once you have published the project on Github you need to maintain it. There are three steps required to upload changes to the Github repository: