Skip to content

Latest commit

 

History

History
80 lines (53 loc) · 3.03 KB

BUILD.md

File metadata and controls

80 lines (53 loc) · 3.03 KB
Raw

BUILD

Build tools required

You can simply install the latest visual studio version (2017 atm).

Or, if you don't want to install everything but just build with build.bat or a third party IDE, you can install msbuild tools :

https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2019

With the following options :

  • MsBuild tools
  • .Net Core build tools
  • Individual components :
    • .Net framework 4.6.1 SKD
    • .Net framework 4.6.1 Targeting pack

Manual build command

build.bat

dotnet builds

Deplying dotnet core apps: https://docs.microsoft.com/en-us/dotnet/core/deploying/.

dotnet restore Oetools.Sakoe/Oetools.Sakoe.csproj
dotnet publish Oetools.Sakoe/Oetools.Sakoe.csproj -f netcoreapp2.2 -c release -r linux-x64 --self-contained --verbosity minimal /p:UseAppHost=true /p:TrimUnusedDependencies=true /p:ShowLinkerSizeComparison=true

.NET Core on Linux relies on the ICU libraries for globalization support.

On centos and rehl, there are some pre-requisites to running even a self-contained application: https://github.com/dotnet/core/blob/master/Documentation/build-and-install-rhel6-prerequisites.md#making-the-libraries-available-for-a-net-core-application.

We can also publish for invariant mode. In this mode, the libraries are not included with your deployment, and all cultures behave like the invariant culture: https://github.com/dotnet/corefx/blob/master/Documentation/architecture/globalization-invariant-mode.md.

A good example project: https://github.com/datalust/piggy.

https://ianqvist.blogspot.com/2018/01/reducing-size-of-self-contained-net.html

tar -zxvf sakoe.tar.gz
cd sakoe
chmod +x sakoe
./sakoe
export PATH=`pwd`:$PATH
sakoe

Additionnal remarks

Why are the libraries like Oetools.Builder targetting explicitly net461 AND netstandard2.0?

This question is legit, according to this net-implementation-support table, we should be able to make our libraries target netstandard2.0 and that's it. Since our application is targetting v4.6.1 and since v4.6.1 implements netstandard2.0 we should be good. But nop! This is explained here :

So yeah. I have to explicitly target net461.

Creating a releasing

  • Update the Version in .csproj, the format should be X.X.X-suffix (with suffix being optional)
  • Create a new tag : git tag X.X.X-suffix
  • Push the tag git push --tags : this will trigger the build with the deployment on the appveyor

Testing with docker

docker run -it --rm --init --name test-sakoe -v /C/data/repo/_github/Oetools.Sakoe/artifacts/sakoe.core.no-runtime:/sakoe mcr.microsoft.com/dotnet/core/runtime:2.2 dotnet /sakoe/sakoe.dll